Two invoices to the same industrial customer show 20 days overdue. One is sitting in the customer’s payment queue waiting for the next run. The other was rejected two weeks ago because the PO covered fewer units than the invoice billed, and nobody on your side saw the rejection notice. A collector can get a date for the first. No amount of chasing will get the second paid.
An invoice is not collectible until the customer’s process will accept it. That depends on four things you can check before sending: the customer has an active supplier record for the right legal entity, the invoice matches a valid PO, it is submitted the way their portal requires, and its tax treatment is supported. This guide covers each gate, plus split billing across subsidiaries, and how to correct a rejected invoice without leaving two versions in collections.
The four gates
| Gate | What the customer checks | Who on your side owns it | Evidence that clears it |
|---|---|---|---|
| Supplier registration | You exist as an approved supplier, under the right legal entity, with verified remit details | Account owner, treasury | Customer confirms the supplier record is active and linked to the PO |
| PO match | The invoice fits an open, funded PO for that entity, period, item, and amount | Billing and account owner | PO number, line, and remaining value checked against the draft |
| Portal submission | The invoice arrived through the right channel with required attachments | Billing | Portal reference and an accepted status |
| Tax treatment | Tax charged, or exemption supported, for this buyer and sale | Tax reviewer | Certificate on file and a decision for this invoice |
Check them in that order. A correct invoice still cannot be accepted by a customer who has no supplier record for the entity that issued it.
Supplier registration
A renewal moves to a different subsidiary on your side, and the customer’s PO still points to your old supplier record. The portal may let billing sign in, but the customer must update its supplier setup before it can process the invoice. Find that out while the account owner still has time to reach procurement.
Check registration on new accounts and whenever the selling entity, the customer’s buying entity, your remit details, or the invoice channel changes. Coupa’s supplier portal, for example, has a setup process for the supplier’s legal entity and an associated payment method. That is a starting point; the customer’s own process decides when the setup is approved and linked to the PO. Coupa’s legal entity setup documentation.
| What billing sees | Who acts | Evidence that closes it |
|---|---|---|
| PO names the old selling entity | Account owner and customer procurement | Corrected PO, or written confirmation of the approved billing path |
| A required supplier document is outstanding | The team that owns the document | Customer confirms it was accepted |
| Portal contact left the company | Portal administrator | New owner can access the correct customer account |
| Remit details changed | Treasury and customer AP | Confirmation through the agreed bank-change verification process |
Keep bank and tax documents in the approved systems. A billing queue can carry the reference and status without copying sensitive details into notes or email.
PO match
Getting the price right will not get the invoice accepted if the buyer’s PO names another entity or period. Before sending, compare the buyer’s PO with the contract and the draft invoice.
| Check before sending | Who resolves a difference |
|---|---|
| PO is current and covers the billed period and amount | Account owner and buyer’s procurement |
| Customer entity and bill-to match the PO | Billing and buyer’s AP |
| Invoice line maps to the ordered item or service | Billing and sales operations |
| Required service acceptance is on file | Delivery owner or customer sponsor |
If the PO has expired or run out of funds, ask the buyer for a revised order. Do not send the invoice and hope; it will come back. Coupa’s portal lets suppliers create an invoice from an existing PO, which helps keep lines aligned, but review customer-specific instructions and compare the resulting lines before submitting. Coupa’s invoice instructions.
When a NetSuite invoice is rejected
Start with three records: the issued invoice, its sales order, and the buyer’s actual PO. The buyer’s PO is what their procurement authorized. Your sales order is what you planned to bill. Decide which one is wrong before changing either.
- PO number missing or mistyped. Confirm the reference with the buyer and follow your approved correction process.
- Wrong legal entity, price, or quantity. The billing owner decides whether the invoice needs a credit and a replacement.
When a correction uses a credit memo, check which invoice it was applied to. Oracle documents that NetSuite lets you apply credit memos to open invoices, including an Auto Apply option that targets older amounts due. If the credit belongs to a specific bill, verify the selection. Oracle’s credit memo instructions.
Portal submission
An invoice in your ledger does not tell you whether the buyer received or accepted it. For each customer portal, keep a short checklist: customer account, PO line, required attachments, submission contact. Before sending, check the file and invoice number against the ledger. After sending, record the portal reference, date, and status, and give someone ownership of watching for a rejection or a missing acknowledgment.
When an invoice is rejected, read the reason in the portal before trying again. A missing attachment, an invalid PO, and a duplicate submission each need a different response. Find out whether the portal allows you to correct the original record, or whether the buyer requires a credit note and replacement invoice; Coupa documents different actions for each. Coupa’s invoice instructions.
Tax exemption certificates
The certificate names the parent company. The renewal invoice goes to a subsidiary. Billing can see the document in the account folder but still needs to know whether it supports this sale.
Record the customer’s legal name, the jurisdiction your tax team identified, what you sold, and the invoice date. Rules vary by jurisdiction. New York, for example, says exemption certificates from other states or countries are not valid for claiming exemption from New York state and local sales and use tax. New York’s exemption certificate bulletin. Have your tax team or tax advisor decide which forms and rules billing should apply; this guide is not tax advice.
| What billing finds | Who acts | What to record |
|---|---|---|
| Tax approved the document for this buyer and sale | Billing | Certificate reference and decision on the invoice |
| Certificate names a different entity | Tax reviewer | Named buyer, invoiced buyer, and why it applies or what replaces it |
| Document missing or incomplete | Account owner and billing | What the customer must provide, who is chasing, next review date |
| Renewal adds a product | Tax reviewer | New lines and the approved treatment for each |
Avoid a blanket exemption flag on a customer record when the decision applies to one entity or one type of sale. If the customer pays the subtotal and disputes the tax, record the received amount and isolate the disputed tax for the tax team to decide.
Split billing across a parent and its subsidiaries
A parent signs the deal and asks you to bill two subsidiaries. The account hierarchy tells you how the companies relate; the agreement and billing instructions tell you who owes each charge. For each charge, record the entity, allocation basis, currency, billing contact, and buyer PO, then reconcile the drafts to the total you intend to bill.
Illustrative rounding example. A $10,000 charge split equally across three subsidiaries gives $3,333.33 each, totalling $9,999.99. Assign the $0.01 to one entity under a documented rule, so the drafts add to $10,000.00.
If the split changes mid-term, record the effective date and keep the old instructions with the invoices they governed. When the parent pays all three in one transfer, use the remittance to identify which invoices it covers. NetSuite’s Consolidated Payments feature can accept payments through a subcustomer or its top-level parent, but that payment option does not determine which entity you should invoice. Oracle’s customer payments documentation. Allocation of that kind of payment is covered in the unapplied cash guide.
Keep the original and corrected invoices connected
Whatever the cause, link the correction to the original invoice in your tracking record. Confirm the buyer received the corrected invoice and accepted it, and record their acknowledgment. Then check that only one version is in the collections queue. A credit-and-rebill that leaves both open will generate a reminder for an invoice the customer was told to discard. Tell collections when ordinary follow-up can resume, and confirm the payment date if the correction moved it.
Measure the gap between send and acceptance
Track the time from planned send date to acceptance, and split delays by cause: registration, PO, portal, or tax. For a pilot, take one new customer and one renewal with a changed entity and ask someone outside the account team to identify the remaining blocker from the billing queue alone. If they cannot, the information is in someone’s inbox. The AR automation guide explains how acceptance fits into the wider receivables workflow, and SaaS billing accuracy covers getting the invoice amounts right in the first place.
Pre-send checklist
- Supplier record active for the issuing legal entity, verified within the last renewal cycle.
- PO current, funded, and matching entity, period, line, and amount.
- Required attachments and service acceptance on file.
- Portal account and submission contact confirmed.
- Tax decision recorded for this buyer and sale, not inherited from another entity.
- Split-billing drafts reconcile to the contract total, with rounding assigned.
- After sending: portal reference, status, and an owner to watch for rejection.
- Any correction linked to the original, with one version left collectible.