What a branch does and does not do to an e-invoice — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for whoever is opening GadgetSphere’s twenty-third branch and has a checklist with an e-invoice line on it. In about ten minutes you will know what the e-invoice pipeline reads from a branch record, what it merely copies from the document, and what it never looks at, so the line on the checklist becomes one flag rather than an afternoon.

Step 1 — See a branch as a place written on the document

After this step you will know what kind of thing a branch is to the pipeline. Every document carries the branch on its header and on every line, beside the company, the store, the profit centre and three more analysis columns — seven places in all, each a column in its own right. That is why a revenue account never needs a branch suffix while a bank account does: a journal line already knows its branch, and a bank balance is reconciled per branch. The e-invoice pipeline sees the branch only as that column. It does not look the branch record up for anything a supplier block needs, because the supplier is the company, and apart from the one flag in the next step it does not use the branch to decide when or where anything is submitted.

Reference: Organization — Branch, profit centre, and the dimensions a document carries

Step 2 — Learn the one branch setting that acts

After this step you will know the whole of the branch’s e-invoice configuration. It is one checkbox, Skip E-Invoice. When a document is finalised, the platform asks whether the document is marked skip, whether its branch is, and whether its customer is; any yes and the document never enters the pipeline, with no queue row, no pool row and no message. The point of sale copies the branch’s flag onto each bill as well, so the cashier’s screen shows the same answer. It is the right control for a branch whose sales are reported by somebody else — a fulfilment location whose orders a marketplace e-invoices, say. Across the whole customer base only a few dozen branches carry it, out of a couple of thousand.

Reference: Organization — Branch Details, Pick Pack, Extension and Marketplace

Step 3 — Know where the branch appears, and where it does not

After this step you can predict whether a branch will be on a finished e-invoice before you open it. On every individual e-invoice the branch code and identifier are copied from the document onto the header, so the great majority of e-invoice records carry their branch and the To IRB listing can be filtered by it. On a consolidated e-invoice built by the common run — the one that groups by company and document type — there is no branch at all, because the run never writes one; a small minority of consolidated headers carry a branch, and those came from the uncommon by-branch run or from a single document rolled up on its own. So a branch is visible on the documents that name a buyer, and invisible inside the one that names the general public.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

Step 4 — Stop configuring the fields the pipeline never reads

After this step three branch fields will leave your checklist. The branch’s own tax registration number is not the service tax number on the e-invoice; the supplier block is built from the company record, and nothing in the e-invoice code asks a branch for its registration. The branch timezone is stored and can be filtered on, and nothing else reads it — the zone every dated process uses is the company’s. And the branch’s default printable is never consulted for the e-invoice PDF, which takes the company’s e-invoice format or a built-in template. Each of these looks like an e-invoice setting on the branch screen, and each is a note to yourself. The company record is where those three facts live.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

Step 5 — Put the branch on the customer’s PDF the one way that works

After this step you will know how a branch gets onto the copy a customer holds. Not through the branch record, and not through the built-in template, which is handed only the e-invoice fields and leaves its logo and address slots empty. A company e-invoice format — uploaded on the company’s E-Invoice tab, one per document type — is handed the company and branch set on top: the branch logo, the branch address and phone from the branch record, beside the company’s own. So the retail company designs one format and every one of its branches prints its own details through it. Two limits: a consolidated e-invoice has no branch, so nothing branch-shaped can appear on it, and the company logo is left blank there deliberately.

Reference: My E-Invoice Admin Applet — What a company format can use

Step 6 — Check the new branch in thirty seconds

After this step the checklist line is done. Open the branch record and confirm the only e-invoice control on it, Skip E-Invoice, is unticked unless somebody else reports this branch’s sales. Finalise one ordinary sale there, then open the To IRB listing and filter by the new branch code: the individual e-invoice appears with the branch on it, which proves the copy. Open any consolidated e-invoice from the common run and read the blank branch column, which proves the absence. And remember that the filter, not a permission, is what narrows this listing — a branch-scoped user who can open it sees the group, and you filter for them.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

How the steps fit together

    flowchart TD
  s1["Step 1 — See a branch as a place written on the document"]
  s2["Step 2 — Learn the one branch setting that acts"]
  s3["Step 3 — Know where the branch appears, and where it does not"]
  s4["Step 4 — Stop configuring the fields the pipeline never reads"]
  s5["Step 5 — Put the branch on the customer's PDF the one way that works"]
  s6["Step 6 — Check the new branch in thirty seconds"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Back to the series · Play this as a presentation