All 220 guides
Every guide opens with a route check: the stage, the data, the validation to expect, and the first check to make. Page 7 of 11, guides 121 to 140.
Status messages and their meanings
Common status messages, what each one commits the sender and receiver to, and what to do on each one.
Validation, errors and corrections explained
Business rules, rejection reasons, credit notes and resubmission, with messages a person can act on.
Actionable rejection design for receivers
What a good rejection message contains, and why a vague rejection wastes both sides time.
Common validation errors and their fixes
Missing fields, wrong codes, total mismatches and identifier errors, each with a fix that does not break another rule.
Corrected invoices vs credit notes: which to use
A corrected invoice replaces, a credit note adjusts, and the choice depends on receiver and tax rules.
Credit notes: full and partial
When to credit in full, when to credit in part, and how each choice affects totals and tax.
Error trends and root causes
Counting errors by rule and field, finding the root cause, and fixing the source instead of each invoice.
Reading a rejection message: from error text to action
How to turn a rejection into a fix: rule, field, value, expected value, and resubmission route.
Resubmission without duplication
Correcting and resending without creating a duplicate invoice, using references and duplicate detection.
Validation layers: schema, business and receiver rules
Three gates in order, what each one catches, and why passing one gate does not guarantee passing the next.
Validation rule change management
When a receiver changes a rule, how to learn, test and migrate without breaking live invoices.
Validation testing before go-live
A test set that covers valid, invalid and edge cases, run against the receiver rules before live exchange.
Onboarding buyers and suppliers explained
Identifiers, channels, test invoices and go-live gates, for each new trading partner, in route order.
Buyer onboarding checklist for a seller
What a seller needs from a new buyer: receiver rule, format, channel, reference and test, in order.
Go-live gates and rollback for onboarding
A gate with pass criteria, and a rollback plan if the first live invoices fail.
Onboarding at scale: many partners without chaos
Templates, a partner register and a routing table, so the tenth partner is as clean as the first.
Onboarding communications that prevent errors
What to tell a partner, when, and in what form, so the first live invoice is not a surprise.
Onboarding for portal buyers
Portal accounts, submission rules and test submissions, kept separate from network onboarding.
Onboarding metrics that matter
Time to first accepted invoice, test pass rate and exception rate, measured per partner, not as a vanity total.
Partner register: fields to keep for each partner
Identifier, format, channel, profile, reference, contact and status, kept current by an owner.