The branch settings that change nothing, and the two that do

Play this lesson as slides — one slide per step, with the same narration. The full text of every step is on this page.

This lesson is the one that saves you the most time, because most of it is work you will now not do. A run of controls on a branch, a location and a company render, save, and are read by nothing at all. Two more are real, and each does something narrower than its name suggests — though one of the two is a good deal more real than you have probably been told. Knowing which is which is the difference between configuring a system and configuring a screen. About thirteen minutes.

Step 1 — Leave Tax Applicable and Pick Pack alone

After this step you will stop configuring two controls that do nothing. The branch Details tab carries a Tax Applicable checkbox that is stored and read by nothing — not by the backend, not by any applet. The Pick Pack tab offers three checkboxes about requiring a delivery quantity balance on sales orders, sales invoices and delivery orders; those are stored too, and no reader exists in the backend or in those three applets. Ticking them changes nothing there. What that does not settle is whether pick and pack can be enforced anywhere else — those same applets carry their own settings for hiding a pick-pack queue — so if somebody asks for enforcement, the answer is that it is not on this tab, and the place to ask is the workflow’s own applet.

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

Step 2 — Do not carry your own codes in the mapping fields

After this step you will not build a process on fifteen fields that go nowhere. Switch on the extension-mapping toggles and a branch gains up to fifteen free-text fields, in five groups of source, table and value. They look exactly like a place to carry your own codes — a legacy branch number, a cost centre, a franchise reference — into posting. They do not go there. The backend offers them only as filters when you query branches, and no posting logic reads them. If a code has to reach a document, put it on the document. And if what you were really reaching for was a second reporting dimension beside the branch, the profit centre from lesson one is the column that already exists for exactly that.

Reference: Organization — Applet settings

Step 3 — Stop looking for a default branch or a default location

After this step you will save an afternoon. Three applets offer a Default Branch and a Default Location under Settings, each with a save button, and in none of them does anything read the value. In the Organisation applet they are stored and no screen pre-selects anything from them, and the Personalization pair there writes into something that was never loaded, so it errors quietly and saves nothing. In Tenant Admin the screen is routed with nothing bound, so the save goes nowhere. In Cashbook they are rendered and not consumed, declared for parity with other applets. There is no tenant-wide default branch.

Reference: Cashbook — Applet settings

Step 4 — Know what the three Disable switches on a company stop

After this step you will know what these three switches guard and what they cannot reach. A company’s e-invoice tab carries Disable Consolidated Submission, Disable Single-General Submission and Disable Consolidated Self Billed Submission. Each removes that value from the Submission Type drop-down on every document of that company, so no clerk can pick it by accident. That is a real control, deliberately placed at the point of choice, and it is the right shape for a distribution company where every sale must be reported individually. Its limit is equally real: it governs what a person may choose. A submission type set anywhere else is outside it, and the consolidation run writes Consolidated onto documents itself without ever consulting the switch.

Reference: Organization — Company E-Invoice tab

Step 5 — Know which high-value setting is the real one

After this step you will stop confusing two controls that share a name and behave differently. The company switch, on the e-invoice tab, is a genuine block: turn it on, and a sales invoice or a sales return of ten thousand ringgit or more refuses to finalise while the buyer’s mandatory e-invoice fields are blank. The point-of-sale key is a separate setting with no toggle on any screen, and it does something narrower: at the same threshold it forces the submission type to Individual and takes single-general and consolidated away. It makes no field mandatory and it blocks nothing, so a large cash sale still finalises with the buyer panel empty. Back office refuses; the till does not.

Reference: POS General — Applet settings

Step 6 — Plan a recovery you can actually run

After this step your recovery plan will be one that happens. When a document was finalised before the configuration it needed existed — the commonest case being a knock-off row that was not enabled at the time — the downstream applet’s search finds nothing. Fix the configuration first: add or enable the row for that company and source type. Then recover the documents already finalised, and there is a real procedure for it, because there is no watchdog and no repair screen anywhere. Put each affected document back to Draft and finalise it again, which re-runs the whole posting chain against the configuration that now exists. Nothing heals overnight, so list the affected documents before you start rather than after.

Reference: Organization — Troubleshooting

How the steps fit together

    flowchart TD
  s1["Step 1 — Leave Tax Applicable and Pick Pack alone"]
  s2["Step 2 — Do not carry your own codes in the mapping fields"]
  s3["Step 3 — Stop looking for a default branch or a default location"]
  s4["Step 4 — Know what the three Disable switches on a company stop"]
  s5["Step 5 — Know which high-value setting is the real one"]
  s6["Step 6 — Plan a recovery you can actually run"]
  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.

Next lesson: Close a branch, and prove the settings · Back to the course