Home
World 50 · Finance Systems · Invoice Lifecycle

How an invoice is created, posted & reimbursed

The journey of one event cost an associate fronts on a personal card — entered in Salesforce, booked in NetSuite, reimbursed through Rippling. Set who owns each field's valid values and watch the reference-data feeds redraw, then export an image to send back.

Who owns each field's valid values?

This is the "dictionary" Salesforce and Rippling use to stamp an invoice. The owner you pick becomes the origin of that field's feeder arrow into Salesforce.

Chart of Accounts is fixed to NetSuite. The open question for Step 1 is the other three — e.g. should Department be owned by Rippling? Pick an owner, or leave it undecided and explain in the notes.

Source of truth — current decisions

Where the valid values for each field come from.

The flow

Bold numbered arrows = the invoice's journey (transactions). Thin dashed arrows = reference data feeding Salesforce.

The lifecycle, step by step

    Label this for handoff

    Your name and any exceptions get stamped onto the exported image.

    If the export button doesn't download (some viewers block it), use your screen-capture shortcut — macOS ⌘⇧4, Windows ⊞⇧S — on the cards above.