From agreed work to a traceable invoice.
An invoice needs more than an amount. The ORQESTRA billing design brings together the agreed work, issuing company, review decision and accounting confirmation.
Finance integration is in development. The billing views shown here are illustrative; recurring billing, delivery and collections require implementation and verification.
Review the draft. Check what happens next.
Northwind’s onboarding invoice is ready for finance review. Follow the draft, the proposed accounting submission and a separate collections queue. The example distinguishes an approved change from a posted or delivered invoice.
Illustrative workflow. Preparation, accounting submission, delivery and payment are distinct stages.
Invoice preparation
Northwind Traders · Example Services (Pty) Ltd
- Reference
- INV-2071
- Currency
- ZAR
- Total
- 48,000.00
- Source
- ERP-ONEXi draft calculation
- State
- Draft — not issued
Illustrative invoice. The source calculation and document revision are reviewed together.
From a won opportunity to an invoice you can trace.
The proposed sequence, from the starting event to the confirmed result.
Select customer and company
Resolve the financial account, issuing company and currency before preparing the invoice.
Explore the capability.
ORQESTRA Finance is being developed around invoice preparation and review. The accounting engine remains responsible for the posted transaction; the surrounding workflow coordinates the people and evidence needed to reach it.
Prepare against the correct account
Identify the customer’s financial account and the company issuing the invoice. Keep the agreed work, currency, quantities and source pricing with the draft.
For a customer served by two companies, confirm which company earned the revenue and which account the invoice will use.
Connected information.
Clear responsibility.
The target design links information across these systems. Each retains responsibility for its own transactions or content.
Define the first
working scope.
Scope one process before committing to a rollout. Agree these requirements and verify the workflow with the people who will use it.
Our implementation approach- Map each operating company and financial account.
- Agree invoice templates, currencies and billing rules.
- Set review and approval responsibilities.
- Validate recurring occurrences, delivery and reconciliation.
Before you connect the work.
Does ORQESTRA replace the accounting ledger?
No. In the target architecture, ERP-ONEXi owns the ledger and financial transactions. ORQESTRA coordinates invoice preparation, approval and follow-up around that engine.
Is multi-company invoicing available?
Production availability is not confirmed. The design separates each issuing company and financial account; the mappings, permissions and accounting workflow must be verified before use.
What should happen after an accounting timeout?
Check whether the source recorded the transaction before trying again. The recovery design requires reconciliation of uncertain results to avoid creating a duplicate; that path must be tested for each integration.
Where does an invoice wait for someone else’s information?
Describe the process, systems and decision-makers involved. Use the enquiry to identify scope, dependencies and what must be demonstrated before use.