The latest articles on DEV Community by Melissa R. Gardner (@melissanovoex). https://dev.to/melissanovoex https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4222657%2Fdc43f349-937e-473a-85c1-35a0cfe10f25.png https://dev.to/melissanovoex en Melissa R. Gardner Mon, 02 Nov 2026 15:33:42 +0000 https://dev.to/melissanovoex/the-fields-on-your-invoice-that-decide-when-you-get-paid-4mol https://dev.to/melissanovoex/the-fields-on-your-invoice-that-decide-when-you-get-paid-4mol <p><em>By Melissa R. Gardner, VP Marketing at NovoEX. Disclosure: I work at NovoEX. This applies to any invoicing tool and any bank.</em></p> <p>Developers tend to treat invoices as admin: generate, send, forget. But your invoice is effectively an input to someone else's system. A client's finance team keys its fields into accounts payable software, and from there into a payment. Bad input, delayed output.</p> <p>Here are the fields that matter most, and the bugs I see in each.</p> <h2> Beneficiary name </h2> <p><strong>Bug:</strong> trading name on the invoice, legal name on the account, or vice versa.<br> <strong>Fix:</strong> use the exact name your account is registered under. Many payment systems compare names, and a mismatch can pause the payment.</p> <h2> Invoice number </h2> <p><strong>Bug:</strong> no number, or numbers that repeat.<br> <strong>Fix:</strong> unique, sequential numbers. Ask clients to use it as the payment reference so you can reconcile without guessing.</p> <h2> Currency </h2> <p><strong>Bug:</strong> amount without a currency, or a currency your account can't receive.<br> <strong>Fix:</strong> state the currency explicitly, and make sure the details you provide can receive it.</p> <h2> Payment details </h2> <p><strong>Bug:</strong> one set of details for every client, regardless of how they pay.<br> <strong>Fix:</strong> include the details for the rail the client will use, such as SEPA for euros or SWIFT for international transfers, and label them.</p> <h2> Due date and terms </h2> <p><strong>Bug:</strong> "Due on receipt", which finance teams often read as "next payment run".<br> <strong>Fix:</strong> a specific date, and payment terms agreed in the contract.</p> <h2> Client legal entity </h2> <p><strong>Bug:</strong> invoicing a brand name rather than the entity that will pay.<br> <strong>Fix:</strong> ask for the legal entity name and address before the first invoice. Payments from a different company than the one invoiced can raise questions on both sides.</p> <h2> Transfer charges </h2> <p><strong>Bug:</strong> silence, then a short payment.<br> <strong>Fix:</strong> one line stating who covers international transfer charges.</p> <h2> A pre-send checklist </h2> <ul> <li>[ ] Name matches account exactly</li> <li>[ ] Unique invoice number</li> <li>[ ] Currency stated</li> <li>[ ] Correct, labelled payment details</li> <li>[ ] Specific due date</li> <li>[ ] Client legal entity correct</li> <li>[ ] Charges arrangement stated</li> </ul> <p>Treat it like a lint step before you hit send.</p> <p><em>Melissa R. Gardner, VP Marketing at NovoEX. Disclosure: I work at NovoEX. General information only, not financial advice.</em></p> <p>NovoEX offers an IBAN in your own name for EUR, GBP and USD, with fiat and crypto in one account. Soft KYC, KYB for businesses. Virtual cards are coming soon. <a href="https://novoex.io/register?ref=A896549E" rel="noopener noreferrer">https://novoex.io/register?ref=A896549E</a></p> career productivity beginners freelance