# Contract-to-invoice mapping

Worked example companion. Fictional scenario; no measured results.

Automate invoice preparation only after the business has agreed what makes an invoice due.

## How to use this sheet

Replace the example rules with your own. Keep each acceptance decision linked to its owner and evidence. Use the blank CSV to record your actual process; the example CSV contains teaching material.

| Source | Destination | Validation |
| --- | --- | --- |
| Signed contract ID + version | Project commercial reference | Approved version exists |
| Billing entity and currency | Invoice customer and currency | Finance confirms the match |
| Milestone ID and amount | Invoice line external reference | One active draft per eligible milestone |
| Acceptance condition | Billing-readiness evidence | Required approval is recorded |
| Amendment | New schedule version | Affected drafts held for review |

## Workflow

1. **Confirm signed scope** (Operations): Billing entity, currency and contract version.
2. **Approve schedule** (Finance): Milestone amounts and acceptance conditions.
3. **Verify readiness** (Delivery lead): Record the required acceptance evidence.
4. **Draft and review** (Finance): Create once, then review before release.

Exception: A changed contract holds affected drafts. A timeout triggers lookup by milestone reference before any retry creates another invoice.

## Measurement

For a comparable set of milestones, record ready_at, draft_created_at, approved_at and sent_at. Log correction time and rejected drafts. Time released is capacity; cash flow and attributable revenue require separate evidence.

## Limitations

- Commercial terms, tax treatment and supported billing correction methods need finance review.
- This example doesn't include a deployed connector or a measured customer outcome.

Source page: https://www.opsautomators.com/work/professional-services-quote-to-cash
Prepared September 7, 2026.