Configure fsConfig for a client
Who does this: Platform Admin · Senior Accountant When: Onboarding a new financial-statements client, or correcting an existing client's defaults. Result:
Client.fsConfigpopulated; the green Setup health gauge on the client page reflects FS readiness; engagement creation succeeds without warnings.
Before you start
- [ ] Client record exists.
- [ ] You hold
MANAGE_CLIENTS.
Required fields
| Field | Format | Example |
|---|---|---|
defaultReportingStandard | SFRS_SE or FULL_SFRS | SFRS_SE |
baseCurrency | ISO 4217 | SGD |
fyEndMonth | Integer 1–12 | 12 |
roundingConvention | String | SGD |
uen | String (ACRA UEN) | 202412345A |
registeredAddress | String | 10 Anson Road #20-01, International Plaza, Singapore 079903 |
principalActivities | String | Wholesale trade in industrial machinery and parts |
Steps
Option A — Web UI
- Open Clients in the staff dashboard sidebar; click into the client.
- Switch to the Financial Statements tab on the client detail page.
- Click Edit fsConfig.
- Fill the form; save.
Option B — API
http
PATCH /admin/clients/<clientId>/fs-config
Content-Type: application/json
Authorization: Bearer <admin-jwt>
{
"defaultReportingStandard": "SFRS_SE",
"baseCurrency": "SGD",
"fyEndMonth": 12,
"roundingConvention": "SGD",
"uen": "202412345A",
"registeredAddress": "10 Anson Road #20-01, International Plaza, Singapore 079903",
"principalActivities": "Wholesale trade in industrial machinery and parts"
}How to know it worked
- The client detail page's Setup health gauge for Financial Statements turns green.
- A subsequent New engagement call defaults the reporting standard and base currency from this config.
- Activity log shows
admin.client.fs_config_updated.