Entity-Level Policy Settings
Most of how REDA behaves isn't fixed — it's a set of business policies you choose, and they can differ from one company to the next. A company in one country might withhold tax and strictly enforce budgets; a company in another might do neither. So these choices live as switches on the entity, where you set each company's policy independently. This article is the catalogue: what each switch does, and — just as importantly — when you'd want it on.
Access you'll need. Changing an entity's policy settings requires the Accounting Admin v2 or Accounting Controller v2 permission set. The Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets can view them but not change them.
Withholding tax
Withholding tax is where the payer holds back part of a payment and sends it to the tax authority on the other party's behalf. It only applies in some countries — so it's off until you switch it on. (New to it? See Understanding Withholding Tax.)
| Setting | What it does | Turn it on when… |
|---|---|---|
| WHT Enabled (Purchase) | Shows the withholding options on purchase documents, so you can hold back tax on vendor payments. | your country requires you to withhold from suppliers/contractors. |
| WHT Enabled (Sales) | Lets the company accept evidence that a customer withheld tax when paying you. | your customers are required to withhold from your invoices. |
| Payer Regime | The company's withholding-tax regime (e.g. Brazil Lucro Real / Presumido / Simples). | your country's rules depend on the company's tax regime. |
Budget & purchasing controls
| Setting | What it does | Turn it on when… |
|---|---|---|
| Enforce Budget Controls | Flips the company from warning mode (the default — over-budget purchase orders are flagged but allowed) to blocking mode, where they're stopped. See Budget Enforcement. | you want a hard stop on over-budget commitments, not just visibility. |
| PO Over-Invoice Tolerance % | How far a vendor bill may exceed the purchase order it's matched to before REDA objects (e.g. 5% to allow small variances). | you match bills to POs and want to allow — or tightly limit — small overages. |
Settlement & reporting
| Setting | What it does | Turn it on when… |
|---|---|---|
| Allow Cross-Entity Settlement (AR) | Lets another company's customer payment settle this company's sales invoice — useful when a group collects centrally. | one group company receives money on behalf of others. |
| Allow Cross-Entity Settlement (AP) | The same on the buying side — another company's payment settling this one's bills. | one group company pays suppliers on behalf of others. |
| Include In Aging | Includes this company in aging snapshots (the reports that show how overdue customer/vendor balances are). | you want this company in your overdue-balance reporting (usually yes). |
Automatic PDF generation
Five independent switches. When on, REDA creates a PDF the moment each document type is posted and attaches it to the record — hands-free paperwork.
| Switch | Generates a PDF when… |
|---|---|
| Auto-Gen PDF: Sales Invoice | a Sales Invoice is posted |
| Auto-Gen PDF: Cash Receipt | a Cash Receipt is posted |
| Auto-Gen PDF: Credit Memo | a Credit Memo is posted |
| Auto-Gen PDF: Purchase Order | a Purchase Order is posted |
| Auto-Gen PDF: Cash Disbursement | a Cash Disbursement is posted |
Turn on the ones whose documents you routinely send out (Sales Invoices and Purchase Orders are the common pair); leave the rest off and generate those on demand.
A worked policy matrix — Meridian’s four companies
Here's how our example group actually uses these switches. Same product, same group — four different policy profiles, because four different countries:
| Entity | Policy choices | Why |
|---|---|---|
| Meridian Properties US LLC | Enforce Budget Controls on; withholding off | The US company runs disciplined procurement — over-budget purchase orders are blocked, not just flagged. US trade payments don't involve withholding. |
| Meridian Properties UK Ltd | Withholding off | UK supplier payments in Meridian's line of business don't require withholding; VAT is handled by the tax engine, not these switches. |
| Meridian Properties India Pvt Ltd | WHT Enabled (Purchase) on | Indian law requires deducting tax at source (TDS) from many vendor payments — the purchase-side switch makes the withholding options appear on its purchase documents. |
| Meridian Properties Brasil Ltda | Withholding on; Payer Regime set | Brazil's retention taxes depend on the company's tax regime, so both the switch and the regime matter. |
Notice what's not different: all four keep Include In Aging on (the group wants every company in its overdue-balance reporting) and none needed a change to any global setting to achieve this — it's all per-company policy.
How REDA applies these
You don't have to do anything beyond setting the switches. Whenever a relevant document is processed, REDA reads the company's policy and acts on it — efficiently, even when posting hundreds of records at once. And if a policy is misconfigured, REDA tells you clearly rather than guessing, in keeping with its "never fail silently" approach. Set the switches once at setup; the engine honours them on every document thereafter.
Your own custom fields stay editable on posted records
Once an accounting document is posted or voided, REDA locks it so the numbers behind your ledger can't quietly change. That protection is essential — but it used to lock the whole record, including custom fields your own admin had added for your own purposes (a project code, an internal note, an approval reference). Those aren't REDA's numbers, and freezing them was more than integrity required.
REDA now locks only what actually affects the accounting:
| On a posted / voided record… | Editable? |
|---|---|
| REDA's own packaged fields (amounts, dates, statuses, GL mappings) | Locked — these are the accounting record |
| Standard Salesforce fields (Name, Currency, Owner) | Locked |
| A field used as a posting-mapping dimension | Locked — it drives where the entry posts |
| A custom field your admin added that is not a posting-mapping dimension | Editable in every state — it's your data, not REDA's |
This applies in every record state — draft, posted, voided, reversal, completed, approved — and needs no configuration; it works the moment you upgrade. Accounting integrity is unchanged: nothing that determines a balance, a posting, or an audited value became editable — only the fields that were always yours to begin with.
Where to go next
- REDA Setup (CMDT) — the org-wide switches above entity policy.
- Entity Fields Reference — where policy toggles live on the record.
- Creating an Entity — set policies while building the company.
- Entity Default GL Accounts — the other big per-entity setup.
Frequently asked questions
Yes. Unlike currency and accounting basis (which lock after posting), these policy switches can be adjusted any time as your business changes — the new setting applies to documents from then on.
The switches start off (or at a neutral default), so REDA does the simple thing: no withholding, budgets track but don't block, no cross-entity settlement, PDFs generated on demand. Turn on only what your business needs.
Because withholding is a country-specific rule, and these settings are per company. That's the whole point of entity-level policy — each company follows its own local requirements.
Budgets are created in the Budgets area. The Enforce Budget Controls switch here decides whether those budgets merely track spending or actively block over-budget purchase orders.
Was this article helpful?