Invoices/2026/Q2/INV-1042_ClientCo
The invoice PDF plus its delivery-method fields: Channel = Portal; Reference = Coupa, submission CSP-88421; Destination = ClientCo Coupa CSP account; Submitted = 2026-04-03; attachment = coupa-confirmation.png.
Invoice lifecycle organization
Invoice Delivery Method Records: How Each Invoice Was Sent
When you bill the same way every time, you never think about it. The moment you have one client on a supplier portal, another who only accepts PDF by email, and a third who still wants a paper copy in the post, "where did I actually send invoice #1042?" becomes a real question. A delivery-method record answers it. For each invoice you store one thing: the channel it went through and the identifier that proves which channel — the portal submission number, the email address it was sent to, or the postal tracking number. Cash Workspace gives each invoice a record where that channel field lives next to the invoice itself, so the answer is always one click away instead of buried in a sent-mail folder or a portal you would have to log back into. This page is about recording the transmission channel only. It is not where you confirm the client received or opened the invoice, not how the invoice was paid, and not proof that goods or work were delivered — those are separate records.
The problem
Why "how was it sent?" is so easy to lose
The delivery channel is one of the few facts about an invoice that the invoice document itself never records. A PDF looks identical whether you emailed it, uploaded it to Ariba, or printed and posted it. The proof of which channel lives somewhere else entirely — in your sent folder, in a portal confirmation screen, on a postage receipt — and those places scatter fast. Weeks later, a client asks "we never got invoice #1042," and you cannot remember whether it went to their AP portal or to an email address that may have been wrong. A single channel field per invoice removes the guesswork.
- The channel is invisible on the invoice document itself, so the only evidence of how it was sent lives in three or four unconnected places.
- Multi-channel clients are the trap: the same client may want a portal upload one quarter and email the next, and you cannot recall which you used.
- Portal submission IDs and confirmation numbers are shown once on a screen and then are hard to retrieve without logging back in.
- Posted invoices have a tracking or certified-mail number that exists only on a paper receipt you will lose.
- When someone else picks up your billing, they have no way to see which channel each client was actually invoiced through.
The workflow
Recording the delivery method after you send
This is a fast, post-send habit: the moment an invoice goes out, capture how it left and the reference that names that channel. It takes under a minute per invoice and turns "I think I emailed it" into a recorded fact. Cash Workspace does not send invoices or watch your portal — you record the channel manually right after you submit.
- 1
Open the invoice record
Find the invoice in its folder (for example Invoices/2026/Q2) and open its record. The delivery-method fields sit on the same record as the invoice file, so the channel is never separated from the document it describes.
- 2
Set the channel
Pick one channel from a fixed list — Portal, Email, or Post — so every record uses the same vocabulary. If a client demanded two routes (uploaded to the portal and emailed a copy), record the primary submission channel and note the second in the channel note.
- 3
Record the matching reference identifier
Capture the identifier that proves that channel: the portal name plus its submission/confirmation ID (e.g. Coupa, submission CSP-88421), the exact email address the PDF went to, or the postal tracking / certified-mail number. This is the field that lets you trace the invoice back to where it landed.
- 4
Attach the channel proof
Attach the screenshot of the portal confirmation screen, the sent-email export, or a photo of the postage receipt to the record. The channel field tells you how; the attachment shows the evidence behind it.
- 5
Date-stamp the submission
Record the date you submitted through that channel. Combined with the channel and reference, this gives you a complete, self-contained line: on this date, invoice #1042 went via this channel, reference X.
Record structure
Fields to record per invoice
Keep the record lean — it documents the transmission channel and nothing more. These are the fields that answer "how and where was this invoice sent?" without straying into receipt, payment, or goods-delivery territory.
- Invoice number
- The invoice this delivery record describes, e.g. #1042, so the channel is tied to a specific document.
- Delivery channel
- One value from a fixed list — Portal, Email, or Post — so records stay comparable across clients.
- Channel reference / identifier
- The proof-of-channel string: portal name + submission ID (Coupa CSP-88421), the recipient email address, or the postal tracking number.
- Submission date
- The date you actually sent or uploaded through that channel (not the invoice issue date).
- Recipient destination
- Where it went: the portal account/vendor login used, the email mailbox (ap@clientco.com), or the mailing address.
- Channel note
- Short free-text for the exceptions: a secondary copy emailed alongside a portal upload, a resubmission to a corrected address, or why post was used.
- Channel proof attachment
- The portal confirmation screenshot, sent-email export, or postage receipt image filed on the record.
Example setup
An example layout
A simple way to keep delivery-method records is right inside each invoice's folder, with the channel captured on the invoice record and a small log so you can scan how everything went out for the period. Here is one workable structure.
Invoices/2026/Q2/INV-1043_NorthApt
Invoice PDF with Channel = Email; Reference = ap@northapt.com; Destination = AP mailbox; Submitted = 2026-04-04; Channel note = cc'd project manager; attachment = sent-email.pdf.
Invoices/2026/Q2/INV-1051_HarborTrust
Invoice PDF with Channel = Post; Reference = USPS certified 9407 1118; Destination = 14 Harbor Rd; Submitted = 2026-04-09; attachment = postage-receipt.jpg.
Invoices/2026/Q2/_delivery-method-log
A one-line-per-invoice summary record: number, channel, reference, submission date — a quick scan of how every Q2 invoice was transmitted, without opening each one.
Common mistakes
Common mistakes to avoid
- Treating the channel record as proof the client received it. Recording "sent via portal" is not the same as confirmation of receipt — keep those concerns separate.
- Leaving the reference identifier blank. "Portal" alone is not traceable; you need the portal name and the submission ID to find it again.
- Logging the channel days later from memory. Record it right after you send, while the confirmation screen or sent email is still in front of you.
- Mixing channel labels — "emailed," "e-mail," "by mail," "posted." Use one fixed set of values so the records sort and scan cleanly.
- Recording the invoice issue date instead of the actual submission date. The delivery record should reflect when it left through that channel.
How it helps
How Cash Workspace helps
Channel field on the invoice record
Each invoice record holds its delivery channel and reference next to the invoice file, so how it was sent is never separated from the document.
Attach the channel proof
Attach a portal confirmation screenshot, a sent-email export, or a postage-receipt photo directly to the record as evidence of the channel used.
Fiscal-year and quarter folders
Organize delivery-method records inside Invoices/2026/Q2 folders so a period's channels stay together and findable.
Export your records
Export the invoice records, including their channel fields, when you hand billing to a teammate or pull a period together for review.
Related
Related pages
Invoice lifecycle stage map
See where the delivery-method record fits among draft, sent, partly-paid, and archived stages, and which folder each lives in.
Invoice resubmission after rejection log
When a portal or client rejects an invoice, track the reason and the corrected resubmission — a step beyond simply recording the original channel.
Client invoicing instructions records
Store each client's required channel, portal URL, and login identity up front, so you know which delivery method to use before you send.
PO-required client tracker
Track which clients require a valid PO before they will accept an invoice through their channel, with the PO document on file.
Unpaid invoice tracker
Keep tabs on which issued invoices remain outstanding, a separate concern from how each one was transmitted.
Payment status tracker
Record where each invoice stands on the path to payment, distinct from the channel it was delivered through.
Finance workflows hub
Browse the full set of invoice-lifecycle and finance-organization workflows Cash Workspace supports.
FAQ
Frequently asked questions
- Does Cash Workspace send invoices or upload them to portals for me?
- No. You send or upload invoices through your own email, the client's portal, or the post. Cash Workspace is where you record afterward which channel you used and its reference identifier. There is no sending, portal integration, or automation.
- Is the delivery-method record the same as confirming the client received the invoice?
- No. This record captures the channel you sent through and its reference — that the invoice went out via a given route. Whether the client received or opened it is a separate concern (proof of receipt / sent confirmation) and is not what this record is for.
- What do I put in the reference field for each channel?
- For a portal, the portal name plus its submission or confirmation ID (e.g. Coupa CSP-88421). For email, the exact recipient address. For post, the tracking or certified-mail number. The reference is what lets you trace the invoice back to where it was sent.
- Can I record more than one channel for the same invoice?
- Record the primary submission channel in the channel field and use the channel note for any secondary copy — for example, uploaded to the portal and also emailed a copy. Keeping one primary value keeps the records consistent and scannable.
What this record is and isn't
This is organizational guidance for documenting how each invoice was transmitted — not tax, legal, accounting, or billing advice. Cash Workspace records the delivery channel and reference you enter; it does not send invoices, does not connect to client portals or your email, does not sync with your bank, and does not confirm receipt, read status, or payment. Recording "sent via portal" documents the channel only and is not proof the client received or paid the invoice. You enter and attach everything manually.
Start recording how each invoice was sent
Give every invoice a home where its delivery channel and reference live right beside the document. Cash Workspace is free to start — create your first invoice folder, add the channel field, and never wonder "where did I send this one?" again. Operated by HELPERG LLC; questions welcome at info@helperg.com.