Completed jobs, deliveries and production records often reach finance as a spreadsheet that looks finished but still needs questions answered. A missing delivery reference, unclear quantity, unconfirmed rate basis or unnamed owner can delay costing, invoicing and reporting.
This Excel operations to finance handover checklist is for the point after operational work is complete. It helps operations prepare a record for finance, gives finance a clear acceptance decision, and keeps incomplete or rejected records visible until they are resolved.
It does not cover sales acceptance before delivery begins. The focus here is completed operational records entering finance.
The handover rule
Sending a workbook is not the same as handing over a record. A handover is complete only when finance has recorded a decision against the completed job, delivery or production record.
For each record, make four things visible:
- the named operational owner
- the named finance receiver
- the current handover status
- any open exception or missing information
Practical rule: If finance cannot see who prepared a record, who reviewed it and what decision was made, the handover is still open.
Operations to finance handover checklist
Use one row per completed job, delivery or production batch. Keep the fields appropriate to your process, but avoid relying on blank cells, informal notes or a separate email thread to explain essential information.
| Checklist item | What to record | Example | Primary owner |
|---|---|---|---|
| Record reference | Unique job, delivery note or batch reference | JOB-1047, DN-5520 or PB-0812 | Operations |
| Record type | Job, delivery, production batch or other completed work type | Delivery | Operations |
| Completion date | Date the operational work was completed | 24 October | Operations |
| Customer, site or cost centre | The code finance uses for reporting or billing | Customer account and site code | Operations |
| Quantity and unit | Completed quantity and its unit of measure | 480 units | Operations |
| Scrap, rework or returns | Relevant quantity details that affect the completed record | 12 scrap units | Operations |
| Labour, materials or other inputs | Information needed for costing or billing | Labour hours and materials issued | Operations |
| Rate or cost basis | The agreed reference used to value the record | Applicable rate card or standard cost reference | Finance |
| Evidence reference | Link or reference to the job card, delivery proof, inspection record or other supporting evidence | Signed delivery note reference | Operations |
| Operational owner | Named person responsible for the operational facts | Named individual | Operations |
| Finance receiver | Named person responsible for the finance decision | Named individual | Finance |
| Handover status | Current status from the agreed list | Ready for Finance | Both |
| Exception note | Missing information, disagreement or follow-up required | Quantity awaiting confirmation | Both |
If a field does not apply, mark it as not applicable and add a short reason. Do not leave a required field blank and assume finance will infer the answer.
Required fields by record type
The core checklist stays the same, but the operational evidence changes with the record.
Completed jobs
For a completed job, finance may need:
- job reference and customer or site
- completion date
- labour hours or other chargeable activity
- materials, parts or subcontracted work used
- rate or cost basis
- job card, inspection record or completion evidence
- named operational owner and finance receiver
Completed deliveries
For a delivery, finance may need:
- delivery note reference
- customer, delivery site and completion date
- delivered quantity and unit of measure
- returns, shortages or damaged goods where relevant
- proof of delivery reference
- billing or cost basis
- named owners and handover status
Completed production batches
For a production batch, finance may need:
- batch reference and product or item code
- completion date
- output quantity and unit of measure
- scrap, rework and yield information where relevant
- labour, machine or material inputs used for costing
- inspection or completion evidence
- named owners and handover status
Currency, only where it matters
If records include values in more than one currency, add the currency code and the agreed rounding treatment to the relevant value fields. For businesses operating only in one currency, this may be unnecessary. The aim is simply to prevent finance having to guess how a value should be interpreted.
Set clear handover statuses
A short, shared status list is more useful than a mixture of colours, comments and informal labels. Keep the definitions clear enough that operations and finance use them consistently.
| Status | Meaning | Set by | Next action |
|---|---|---|---|
| Ready for Finance | Operations has completed the required information and submitted the record for review | Operational owner | Finance checks the record |
| Accepted | Finance has reviewed the record and can use it for the relevant finance process | Finance receiver | Record proceeds normally |
| Accepted with exception | Finance can proceed, but an identified issue remains open and visible | Finance receiver | Exception is tracked to resolution |
| Incomplete | Required information or evidence is missing | Finance receiver | Returned to operations with the missing item stated |
| Rejected | The record conflicts with supporting information or cannot be accepted as submitted | Finance receiver | Returned to operations with the reason recorded |
Finance acceptance should be a named decision, not an assumption based on the absence of a reply.
Assign owners on both sides
Every record needs a named owner in operations and a named receiver in finance.
- Operational owner: responsible for the accuracy and completeness of operational facts, including quantities, dates and evidence references.
- Finance receiver: responsible for deciding whether the record is accepted, incomplete, rejected or accepted with an exception.
- Backup owner: an agreed alternative contact when the usual owner is unavailable.
Using department names alone, such as “operations” or “finance”, makes it difficult to resolve a record that is waiting for action. Record named people against the handover, while keeping responsibilities clear between the two functions.
How finance should handle incomplete and rejected records
The finance team should not silently correct operational facts just to make a report or invoice progress. If a quantity, date, evidence reference or other key detail is wrong or absent, return the record to the operational owner with a clear reason.
A simple exception register can sit beside the handover list. It should show:
| Field | Purpose |
|---|---|
| Record reference | Identifies the affected job, delivery or batch |
| Exception type | Explains whether the item is incomplete, rejected or otherwise unresolved |
| Description | States what is missing or inconsistent |
| Operational owner | Shows who needs to respond |
| Finance owner | Shows who is monitoring the issue |
| Date raised | Shows when the issue entered the queue |
| Current status | Shows whether the item remains open or has been resolved |
| Resolution note | Records the agreed outcome when closed |
Keep exceptions visible until they are resolved. This is particularly important where finance can proceed with part of a record but a follow-up item remains open.
Worked examples
A completed job accepted by finance
A job record includes its job reference, completion date, customer code, labour information, materials used and a linked completion record. Operations marks it Ready for Finance. Finance checks the rate basis and supporting evidence, then sets the record to Accepted.
The important point is not that the job had no questions. It is that the finance decision is visible on the record rather than buried in an email.
A delivery returned as incomplete
A delivery note has a valid reference and quantity, but the proof of delivery has not been recorded. Finance sets the status to Incomplete and identifies the missing evidence. The operational owner adds the reference and resubmits the record for finance acceptance.
A production batch rejected for clarification
A production batch record states an output quantity that does not match the supporting production information. Finance marks it Rejected with a short reason. Operations checks the source information, corrects or explains the discrepancy, and sends the record back through the same acceptance step.
When an Excel checklist is enough
Excel can be a sensible way to run this checklist when the process is stable, the handover volume is manageable and the people involved can consistently maintain the required fields and statuses.
The workbook becomes harder to manage when completed records are repeatedly copied between files, finance spends time chasing missing information, exceptions disappear into email, or different teams use different versions of the same status rules.
A repeatable handover is not just a spreadsheet layout. It is a sequence of operational decisions: prepare, review, accept, return or hold for an exception.
When a managed workflow may be a better fit
A managed custom web application can be worth considering when your operational spreadsheet has become the working process for multiple people and recurring handovers. It can be designed around your own job, delivery or production records, required fields, finance acceptance decisions and exception handling.
Spreadsheet Upgrade provides fully managed custom web applications that replace business-critical operational Excel workflows. If you are evaluating that move, read our guide on replacing Excel with a web app.
For broader commercial information, see the pricing page.
Before you change the process
Use this final check against one recent batch of completed records:
- Can every record be linked to a unique job, delivery or batch reference?
- Does every record have a named operational owner and finance receiver?
- Are required quantities, dates, evidence and valuation inputs complete or explicitly marked as not applicable?
- Can finance record an acceptance, rejection, incomplete status or open exception on the record?
- Can a manager see which records remain unresolved and who owns the next action?
If several answers are no, the issue may be the workflow rather than the spreadsheet formatting. A Free Fit Check is a starting point for discussing whether the process should remain in a controlled workbook or be replaced with a managed custom application.