Get Your Invoice to Accounts Payable Without It Vanishing

You send an invoice to your day-to-day contact at a client. That person does not pay you. They forward your PDF to someone in finance, or they mean to and forget, and three weeks later your 30-day invoice is 50 days old with no one able to say where it went. The handoff between your contact and the people who cut the payment is where invoices die.

JupiterInvoice moves that handoff onto the invoice itself. Your contact does not have to draft a forwarding email or dig up the AP address from memory. They open the link, name the accounts payable contact, and forward it in place. Here is how that actually plays out, step by step.

Step 1: Your contact opens the link and sees a live invoice

You create the invoice, generate a private link, and send it. Your contact clicks it and lands on the invoice with no login, no signup, and no PDF to download first. They see line items, amounts, your bank details, and the payment terms. This matters for the forward, because whoever they pass it to opens the same live document, not a screenshot of it.

If you want to confirm the link was opened before you assume it stalled, view analytics tell you when it was viewed. That is your signal that the invoice reached a human and the ball is now in their court.

Step 2: They add the PO number and check the billing entity

Before an invoice reaches AP, two things usually need fixing. First, the purchase order number. Many AP teams will not pay an invoice that does not carry a matching PO, and your contact often knows that number when you do not. They type it straight into the PO field on the link. You get notified, and if it looks wrong you can revert it.

Second, the billing entity and address. The legal name a large client pays under is frequently different from the brand name you know them by. Your contact updates the billing entity, billing address, and if needed corrects the details so the invoice matches what AP has on file. If your invoice already shows the wrong billing details, this is where they get fixed without a new round of email.

These are amendments to the current version, not new versions. The PO number and billing edits attach to the invoice as it stands. Content changes like pricing or terms work differently and create a new version, which keeps the audit trail clean.

Step 3: They set the accounts payable contact

Now the part this comes down to. On the invoice link, your contact sets an AP contact: the name and email of the person or shared inbox in finance that handles vendor payments. This is one of the recipient-editable fields, so they enter it directly.

Setting the AP contact does two things. It records, on the invoice, who is responsible for paying it, so there is no more "I thought Priya was handling that." And it gives the forward a destination. Without a named AP contact, forwarding is a guess. With one, it goes to the right place.

If you want the full mechanics of this from the recipient's side, the walkthrough on forwarding an invoice to accounts payable covers what your contact sees at each field.

Step 4: They forward the invoice from the link

With the AP contact set, your contact forwards the invoice. This is not a manual email with your file attached. It sends the AP person the same private link to the same live invoice. AP opens it, sees the PO number, the correct billing entity, the line items, and your bank details, all in one place. Nothing was retyped, so nothing got mangled in translation.

AP can then run their own checks against the invoice. If you want to see what those checks look like from their side, the accounts payable invoice approval checklist lists what they verify before they release payment. Meeting those requirements up front is the difference between a smooth approval and a rejection that sends you back to square one.

Step 5: AP requests changes or approves

If AP needs the currency changed, a due date adjusted, or a line item corrected, they submit a change request rather than editing your numbers directly. You approve or decline it. If you approve, a new version is created, and the invoice status moves to Change Requested and then forward again. If everything checks out, AP approves the invoice, at which point that version locks permanently. An approved, locked invoice is a settled reference both sides can point to.

Certain fields never move through any of this. The invoice number, the issue date, your sender details, and your bank details are locked once the invoice is issued. AP cannot alter where the money goes, which is exactly the boundary you want when a document is passing through several hands.

Why the link beats the forwarded PDF

A forwarded PDF is a dead end. Once it leaves your contact's outbox you have no idea whether it reached AP, whether the PO was added, or whether someone quietly retyped your bank details and got a digit wrong. The back-and-forth that a static PDF creates is the reason Net 30 invoices routinely pay at Net 50.

Keeping the invoice as a single live document means the PO, the billing entity, the AP contact, and the forward all happen on one record you can watch. When you next wonder why an invoice is taking so long to get paid, you can see exactly where it stopped instead of guessing.

Set up your invoice so your contact can do all of this in a few clicks. Create the invoice and generate the link, and hand the AP handoff back to the people who know their own finance team.