A project invoice's accounting date determines when the invoice posts to the financial records. It does not determine when the customer will pay. For a four-week collections forecast, preserve the accounting date as a source fact, but assign an expected collection week from invoice status, due date, customer evidence, approval state, and other current timing support.
Microsoft's Project Operations documentation explains that the invoice accounting date drives the financial period for billed sales postings and can differ from transaction and document dates. Its invoicing process overview distinguishes operational work, pro forma review, confirmation, and the posted customer invoice. Those dates serve different jobs.
Keep the date fields explicit
| Date | Operational meaning | Four-week use | | --- | --- | --- | | Work or transaction date | When the underlying service or cost event occurred | Upstream context only | | Document or invoice date | Date on the customer-facing invoice | Identify the issued record | | Accounting date | Period in which the posting enters the ledger | Reconcile the financial source | | Due date | Contractual or configured payment deadline | One timing input, not a receipt promise | | Expected collection date | Current management judgment from evidence | Assign to the forecast with a label | | Receipt date | When payment is observed | Record actual cash and variance |
Collapsing these fields into one date can make a clean month-end posting look like cash evidence. It can also hide a customer delay when the accounting date was adjusted for period alignment.
Start from the posted invoice
Professional-services teams often track work in progress, approved time, expenses, milestones, pro forma invoices, and confirmed customer invoices. Only the issued open invoice belongs in the invoice-level receivables population. Earlier workflow dates can explain how the amount was created, but they do not become an open receivable on their own.
For each invoice, preserve the project or engagement reference, invoice identifier, document date, accounting date, due date, open amount, customer approval evidence, current collection assumption, internal owner, and review date. If the accounting date changes, retain the earlier snapshot and the reason supplied by the authorized system.
The billing-backlog boundary keeps ready-to-bill work separate from posted receivables. The unbilled-sales comparison covers the same boundary for operational actuals.
Reconcile period changes without moving cash automatically
An accounting date may move into a different open period while the invoice date, due date, and customer workflow remain unchanged. Do not move the expected cash week solely because the ledger posting period changed. Conversely, a new customer commitment or approval may improve timing evidence without changing the accounting date.
When comparing forecast snapshots, label whether a variance came from a changed source date, a changed open amount, or a changed collection assumption. That makes the history reproducible and prevents a period-close adjustment from masquerading as a collections update.
Decision rule
Use the accounting date to reconcile when the invoice posted. Use the due date and current customer evidence to review when cash may arrive. Keep both fields, and never substitute one for the other.
AR Pulse analyzes an authorized receivables export for B2B service firms and builds an invoice-level cash-action view. It does not edit project systems, interpret contracts, or promise cash timing. Apply for AR Pulse when source dates and collection assumptions need a traceable bridge.