AEC ERP

Acumatica Navigation: Dashboards, Inquiries & Reports

Acumatica Navigation: Dashboards, Inquiries & Reports

With hundreds of dashboards, inquiries, and reports in Acumatica, you can access real-time information on your company, displayed in various presentation forms, allowing for quick data analysis. But what exactly are dashboards, inquiries, and reports?

Impact of Allocation Mode on Non-Stock Items used for Projects in Acumatica

Impact of Allocation Mode on Non-Stock Items used for Projects in Acumatica

If you have project commitments for non-stock items such as services and expenses, keep the following in mind when you are handling a price variance on the AP Bill that is different from the Purchase Order and how that impacts your projects.

New in Acumatica Advanced Expense Management

New in Acumatica Advanced Expense Management

Advanced Expense Management automates the creation of expense receipts for designated corporate credit cards by auto-generating expense receipts for you from your credit card transactions.

Difference Between Task and Project Task on the Time Card in Acumatica Cloud ERP.

Difference Between Task and Project Task on the Time Card in Acumatica Cloud ERP.

A customer recently asked us about the difference between Task and Project Task on his Time Card. His organization uses Project Accounting and every employee submits time cards for billable hours (i.e., working on project tasks). For non-billable hours (e.g., staff meeting), they book them to project X. Task seems like a redundant field so he hid it from view.

Getting Multiple Approval Maps to Work Concurrently on an Entity in Acumatica ERP

Getting Multiple Approval Maps to Work Concurrently on an Entity in Acumatica ERP

I recently explored ‘stacking’ approval maps to address a customer’s business process requirement. The use case is to allow all approvers to be notified and move specific documents, such as Purchase Orders or AR Invoices, through approval ASAP. For starter, the steps in an approval map work sequentially. This results in one user (or workgroup) being notified when a step is triggered but approvers in subsequent steps will not be notified until preceding conditions have been satisfied. In other words, the customer wants the notification to reach different teams at the same time.