Article
After Signing, Track Payment, Delivery and Acceptance
After a contract is signed, pull payment, delivery and acceptance out of the text into a tracking plan: for each item, write the due date or trigger, the evidence to keep, who is responsible, and the current status, and hang the plan on the same ledger record, not in a personal spreadsheet. Payments should follow a receipt-and-payment plan, and there should be no payment without a contract; delivery and acceptance each need their own evidence, the three often trigger one another, and a supplemental agreement that changes a milestone should change the same plan. That is what you can go back to when reconciling accounts or when a dispute arises.
- By
- Zico Team
- Published
7 min read
The short version
zico.fim.ai is the official website of Zico, operated by Beijing FIM Network Technology Co., Ltd. Signing a contract does not mean payment, delivery and acceptance will happen on their own. If these three things stay only in the signed text and in people's heads, they often fail to line up when due: a payment is missed, goods arrive without an acceptance record, or acceptance is done but the payment cannot be matched to a milestone.
After signing, pull a fulfillment tracking plan out of the contract: list payment, delivery and acceptance separately; for each item, write the due date or trigger, the evidence to keep, who is responsible, and the current status; and hang the plan on the same ledger record as the contract. The plan follows the contract, not a personal spreadsheet. When a supplemental agreement changes a milestone, change the same plan.
1. Pull three kinds of milestones from the signed contract
Payment, delivery and acceptance should be taken item by item from the signed text (including annexes and supplemental agreements already in force), not filled in from memory:
- Payment: amount or percentage, conditions (for example, acceptance passed, invoice received), and the payment deadline;
- Delivery: what is to be delivered, quantity, specification, time, and place or method;
- Acceptance: the standard, the period for completing acceptance, what happens if acceptance fails, and whether silence after a deadline is treated as acceptance.
The three often hang on one another, for example "payment within a set number of days after acceptance", or "acceptance within a set number of days after arrival". Write those links down when you extract the milestones, so later work does not watch only one of them. Some contracts also have retention money, delivery in stages, or acceptance in batches; list the milestones that will actually occur, rather than forcing one item into each of the three categories.
2. Write four things for every milestone
For each milestone, write down four things:
- Due date or trigger: a calendar date, or an event after which the item becomes due;
- Evidence: invoice, payment receipt, delivery note, signed receipt, acceptance certificate, written objection, or whatever that milestone actually requires;
- Owner: which of finance, the project or business team, and legal follows which kind of item;
- Status: not yet due, pending, completed with evidence attached, overdue, or partly completed.
Keep these four fields in the contract ledger, or in a fulfillment record linked to that ledger entry. If they live only in the handler's own spreadsheet, they fall apart when that person leaves or changes role.
3. Payment: follow the plan, and do not pay without a contract
Payment tracking should run against the plan, not against a payment request that then sends people looking for the contract. When a payment is requested, first find the contract and the matching payment milestone, check how much is due, whether the conditions have been met, and whether the evidence is complete, and only then proceed. If there is no matching contract, or the contract has not finished signing, the payment should in principle not be made. That is the common rule of "no payment without a contract".
Every payment already made should be written back to the plan: how much, on which date, and under which evidence number. What is still payable, what has been paid, and what is overdue can then be seen in one place.
4. Delivery: keep evidence of what, when and where
Delivery tracking should answer: what was agreed, whether it was delivered, whether it matched the agreement, and on which date. Evidence is usually a delivery note, a signed receipt, transport documents, or, for services, a confirmation of work done. If quantity or specification does not match the contract, record the difference at the time; do not wait until acceptance or payment to fill it in.
If delivery is in batches, track it by batch. Do not record only a single "delivered".
5. Acceptance: watch both the standard and the deadline
Acceptance tracking should state the standard, the period for completing acceptance, and who is authorized to issue the acceptance opinion. If the contract says that failure to object within a period is treated as acceptance, mark that deadline on its own, and make sure someone acts before it passes.
Record the result as passed, failed, or partly passed, and attach the acceptance certificate or a written objection. For a partial pass, write down the scope that passed and what will be done with the part that did not, so payment later does not turn into two conflicting stories.
6. Look at the three together
Do not keep payment, delivery and acceptance on separate sheets. Many payment conditions are "delivery completed" or "acceptance passed"; a failed acceptance can hold back a payment; late delivery may trigger a deduction or termination. When one tracking plan shows all three kinds of milestones and the links between them, finance, the business team and legal are looking at the same record.
How to match the paper original, the scan and the electronic final copy after signing is covered in Archiving Signed Contracts: Originals, Scans and E-Copies. Archiving answers "where the contract itself is kept"; fulfillment tracking answers "whether the work after signing was done". Both are needed; neither replaces the other.
Dates that belong to expiry, renewal or termination notices are a different set. See Expiry reminders: renewal, termination and auto-renewal. Expiry reminders watch the term of the contract; fulfillment tracking watches whether payment, delivery and acceptance were completed as agreed. Some payment or acceptance milestones fall before the expiry date, so both kinds of dates may sit on the same ledger record, but a single expiry date should not stand in for fulfillment tracking.
7. Record what happens when things do not line up
Late delivery, failed acceptance, or a payment request before the conditions are met should all be written on the plan: what happened, which clause it rests on, and whether the next step is to complete delivery, pay in part, make a change, or move to a claim or termination. If the only record is a spoken "let's do it this way" or a chat message, it is hard to reconstruct later.
If a supplemental agreement or change order revises the amount, the deliverable or the acceptance standard, update the tracking plan at the same time, and note which supplemental agreement it follows.
FAQ
If the payment plan and the signed text do not match, which one governs?The signed contract text (including supplemental agreements already in force) governs. Amend the plan to match the text, and record who changed it and on which date. Do not use the plan to rewrite terms already agreed.
Can we pay before acceptance has passed?It depends on the contract. If the condition for that installment is that acceptance has passed, that installment should not be paid before acceptance is complete. If the contract clearly provides for an advance or for payments against progress, pay against the matching milestone, and mark on the plan which milestone this payment belongs to and which later evidence is still missing.
Can fulfillment tracking live in the handler's spreadsheet?It can serve as a short-term stopgap, but it is easy to lose when people change roles or when many contracts run at once. The tracking plan should hang on the contract's ledger record, so finance, the business team and legal can all see the same copy within their permissions.
If the other party delivers late, do we still pay on the original date?First check whether delivery and payment are linked in the contract, and what the contract says follows from late delivery. Record the actual delivery date, any written notice, and the clause you are relying on, then decide whether to pay as planned, hold the payment, or deduct as agreed. Do not leave that decision only in a chat history.
What can Zico do for tracking payment, delivery and acceptance?The Zico (FIM) contract system covers drafting, negotiation, approval, signing, fulfillment and archive. For fulfillment and internal control it provides receipt-and-payment plans, no payment without a contract, governance of backdated signing, and operation audit logs; for the ledger and archive it provides a contract ledger and search. The system is delivered as a private deployment, priced per project, with no limit on the number of accounts, and first-year maintenance included at no extra charge. See the feature list on Zico Contract System: draft, approve, register, fulfill.
Summary
After signing, pull payment, delivery and acceptance into a tracking plan; write the condition, evidence, owner and status for each item; and hang the plan on the same ledger record. Payments follow the plan, and there should be no payment without a contract; delivery and acceptance keep their evidence; the links among the three are watched together; changes and disputes are recorded on the same plan. Archiving and expiry reminders are separate tasks, and neither takes the place of fulfillment tracking.
Related
- How to Keep a Contract and Its Amendments AlignedAfter a contract is amended or a supplement is signed, keep the original and the amendment under the same contract number and the same register record…
- Before Signing: Which Counterparty Documents to CollectBefore signing, collect the counterparty's registration documents, signing authority, and the signatory's ID; if the work requires a permit…
- Group Subsidiaries: Splitting Contract Permissions and DataWhen a group has several subsidiaries, don't configure contract permissions person by person. Build one table first: organization down the side (group…
Bring these questions to a demo
Book a dedicated demo and walk one complete path matching your organization, collaboration platform and deployment requirements.