The Invoice, Contract and Payment Do Not Match. How Should You Investigate?

The people, business and events in this lesson are fictional teaching examples, not the firm's clients or actual engagements. Manager Lin's company buys a software service through a platform. The supplier's name appears on the contract and invoice, but the payment page shows a platform settlement account. Chen in finance asks whether the transaction must be rejected because the invoicing company is not receiving payment directly. Operations points out that staff are already using the software.

A contract records agreed obligations, a Chinese tax invoice is a legally regulated business receipt or payment voucher, and bank records show how money moved. They answer different questions. Comparing the business, invoice and payment flows is a useful practical check, but it cannot replace analysis of the actual transaction and applicable tax conditions. Documents that appear consistent do not, by themselves, prove that a transaction occurred.

Finance normally works with the business team on this review and may engage tax professionals for complex matters. The company supplies contracts, orders, delivery records, invoices and payment evidence. The reviewers identify roles, compare records and check the rules. Their output explains differences, missing evidence and proposed payment, invoicing or tax actions. Professional advice does not constitute approval by the tax authority.

First, identify six roles

Chen does not start by asking everyone to make the names identical. She identifies the buyer, contracting party, actual service provider, invoicing party, payer and ultimate recipient of the money. She also establishes who uses the software and who bears its cost. One company may perform several roles; a settlement arrangement may separate others.

The platform might collect money for a supplier, or it might itself be the seller. Those situations have different invoicing implications. Chen requests the order terms, settlement arrangements and supplier's supporting information and compares them with what actually happened. A payment screen displaying the word platform does not establish a valid collection arrangement on its own.

Second, connect the service and payment through one order

The review begins with a single order reference. The purchase request explains why the software was needed. The contract and order identify the purchase and buyer. Activation and usage records explain delivery. The invoice and payment records link the amount, date and parties. If the platform collects on behalf of another party, records must explain its role, authority and settlement relationship.

The records will not all be held by finance. Procurement knows what was ordered, users know what they received, and the platform holds payment and settlement information. Chen arranges the material in sequence and marks what is supported and what remains missing. One screenshot of a bank transfer cannot answer every question.

A genuine arrangement between several parties may explain different names, but the applicable invoicing and tax requirements still need review. This fictional example demonstrates a method. It does not mean that platform collections, group payments and employee advances all receive the same treatment. Different facts and roles require different judgments.

Third, separate three questions often hidden inside 'Can we book it?'

The first question is accounting: how should the actual transaction be recorded under the applicable accounting rules? A transaction that occurred should not be erased merely because an invoice is under review. Equally, possessing an invoice does not justify recording expenditure that never occurred. The accounting needs to reflect the facts.

The second is corporate income tax deductibility: can the expense reduce taxable income? The voucher rules require authentic, lawful and relevant support, together with related records such as contracts and payment evidence. Where an invoice is legally required, a business cannot simply decide that a bank statement replaces it. Missing or non-compliant vouchers call for a review of the prescribed correction conditions.

The third is input VAT credit: under the general VAT calculation method, qualifying input VAT may be credited against output VAT as prescribed. Articles 16 and 22 of the VAT Law and the implementing regulations address supporting documents and exclusions. The purchase, type of voucher and use must be checked. Income tax deductibility does not automatically establish a VAT credit.

Fourth, check that the invoice reflects the actual buyer and business

Chen checks the buyer, seller, service description and amount on the invoice. Article 37 of the VAT implementing regulations requires an invoice to the purchaser for a taxable transaction. Who pays on another party's behalf does not, by itself, determine the buyer's name on the invoice. The actual relationships and relevant rules must both be considered. Incorrect information needs correction through the proper procedure.

The invoice administration rules prohibit invoices inconsistent with the actual business. If a company did not provide the relevant supply but is brought in to issue an invoice, an additional payment explanation does not resolve that problem. Conversely, verifying that an invoice exists answers only part of the question; it does not replace checking whether the service was delivered.

Electronic and paper invoices have equal legal effect. An electronic invoice requiring correction should follow the applicable credit-invoice procedure, rather than having its buyer's name edited in a downloaded file or screenshot. VAT matters in 2026 must be assessed with the VAT Law and implementing regulations now in effect, not solely by citing the former interim regulations.

Fifth, complete genuine records and assign unresolved issues

Where records are simply scattered, Chen asks colleagues to assemble the orders, authorisations, delivery and settlement evidence that genuinely existed and explain their connections. A supplementary explanation may record the actual sequence of events. It must not invent a payment mandate, backdate an agreement contrary to the facts or change service dates to a preferred version. Neat paperwork cannot substitute for reality.

An invoicing party with no relevant role, an undelivered service, an unexplained receiving account or a refusal to supply basic evidence should be escalated. For payments not yet made, any temporary hold needs consideration of the contract and internal controls. Transactions and payments that already occurred must remain in the records, with errors handled properly rather than deleted.

A transaction checklist is more useful than a slogan

Manager Lin receives a table covering the order, parties and roles, actual delivery, invoice details, payment route, explanations, missing documents, owners and due dates. It helps determine the next action and provides a useful information checklist for similar future purchases.

When names or amounts differ, first establish whether the business occurred, then whether the relationships are evidenced, and finally assess accounting, corporate income tax deductions and VAT credits separately. Different names alone do not establish a violation. Identical names do not justify skipping the review. The decision needs real events, connected evidence and the applicable rules.