The line-item format that stops procurement splitting your brand-deal fee

Brand procurement teams are not trying to cheat you. They're trying to fit your invoice into a system that was built for buying office furniture and software licences, not a $12,000 YouTube integration. When your invoice is vague, their system forces the split. The fix is formatting, not negotiation.

Why procurement splits your fee in the first place

Most enterprise finance systems require every purchase order line to map to a single budget code: "media spend," "production," "agency fees," "content creation." When your invoice arrives as one line — "Brand partnership fee: $12,000" — and the campaign manager tagged the deal as partly production and partly media, accounts payable flags it for reclassification.

That flag triggers a review. The review takes two weeks. Suddenly your NET 60 is a NET 74, and no one on the marketing side has visibility into why.

The deeper problem: procurement didn't negotiate your deal. Marketing did. The contract language your marketing contact agreed to often doesn't match the purchase order that procurement raised. Your invoice arrives into a bureaucratic gap between those two documents.

The budget code your invoice should reference

Before you send anything, ask your marketing contact for the PO number and the cost centre or budget code attached to it. Most creators skip this step because it feels like extra admin. It isn't. It's the difference between a 60-day wait and an 83-day wait.

Once you have it, that code goes on your invoice. Not in the notes field. On its own labelled line or in the invoice reference field, where AP software actually reads it.

The three-field line-item structure that closes the gap

The goal is to make your invoice self-classifying. Procurement should be able to process it without referring back to marketing for clarification. Here's the format that does that:

Line 1: Content creation and production Description: "Video production — 1x integrated YouTube video (60-second segment), per SOW dated [date], PO# [number]" Amount: $X

Line 2: Usage and distribution licence Description: "30-day paid amplification licence — usage rights for paid social, per SOW dated [date]" Amount: $X

Line 3 (if applicable): Exclusivity fee Description: "Category exclusivity — [category], [start date] to [end date], per SOW dated [date]" Amount: $X

This structure works because each line maps cleanly to a single budget code. Production goes to production. Licence fees go to media or licensing. Exclusivity goes to whatever brand protection budget they run. AP can process each line independently without flagging the whole invoice for reclassification.

Reference the SOW, not the contract

Contracts are legal documents that procurement may not have access to. The Statement of Work (SOW) is the operational document that should be attached to the PO. Always reference the SOW date, not the contract date. If your deal didn't include a formal SOW, get your marketing contact to email you a written brief and treat that email date as your reference. Any document anchor is better than none.

What to do when the PO doesn't match your invoice total

This happens more than it should. Marketing agreed to $12,000. Procurement raised a PO for $10,000 because someone miscoded the deal or hit a budget ceiling. You're now invoicing against a PO that doesn't cover your full fee.

Do not adjust your invoice to match the PO. Invoice your full contracted amount and include this line in the invoice notes: "Invoice total reflects contracted fee per SOW dated [date]. If PO does not match, please contact [marketing contact name] at [email] to issue a PO amendment before payment processing."

That single sentence routes the problem to the right person inside the company. It also creates a paper trail that protects you if the dispute drags past your payment terms.

The payment terms field that stops the clock from starting late

Even a perfectly structured invoice can stall if procurement logs the receipt date as the date they processed it rather than the date you sent it. NET 60 should start the day the invoice lands, not the day someone opens it.

Add a line to your invoice notes: "Payment terms: NET 60 from invoice date [date]. Due date: [date]." Write the due date explicitly. Don't leave it as a calculation for AP to do. ZenPay lets you set payment terms presets (Net 30, Net 60, Net 90, or custom days) so the due date is always printed on the invoice itself, with no arithmetic required on either side.

When the due date is printed and your auto-reminders are scheduled to fire a few days before it, you're not chasing anyone. You're just confirming a date that was already agreed.

One last thing to send alongside the invoice

Attach the relevant SOW page as a PDF alongside your invoice. Not the full contract. Just the page that shows the deliverable description, the fee, and the payment schedule. This single-page attachment means AP can match your invoice to the PO without going back to procurement, who goes back to marketing, who goes back to you.

Most of the delay in brand deal payments is not bad faith. It's document gap. Close the gap at the point of sending, and you pull a meaningful number of days off that NET 60.