SNCO Consulting insights for Malaysian business technology

SCSB explains why Business Central's minimum-invoice-amount field cannot identify Malaysia's RM500 small-value withholding tax batches, and what can.

SCSB explains why an SST audit file export is only as good as the posting groups, dimensions and retained records underneath it in Business Central.

SCSB explains why Business Central's default posting date doesn't match RMCD's cash-basis trigger for self-assessed SST-02A reverse charge on imported services.

SCSB explains why tracking approved versus consumed quantity matters for Schedule C sales tax exemption purchases inside Dynamics 365 Business Central.

SCSB explains which PDPA 2010 principles actually translate into Microsoft 365 settings, and the label taxonomy, policy scope and licensing decisions that follow.

SCSB explains why a Business Central deployment's existing document sending setup, not transaction volume, decides which MyInvois integration model is reachable.

SCSB maps HASiL's credit note, debit note and refund note rules onto Business Central's document types — and the gap where no debit memo exists.

SCSB explains how section 245's retention, location and availability requirements map onto Microsoft Purview label design, record types and data residency choices.

SCSB explains why Business Central's straight-line depreciation does not match Schedule 3 capital allowance, and which second-book structure keeps both bases reconciled.

SCSB maps Business Central's self-billed invoices, CP58 and 2% s107D withholding tax onto a single agent commission payment for Malaysian companies.

SCSB explains why SST-02 preparation in Business Central depends on posting-group accuracy, period controls and reconciliation, not on the report alone.

SCSB on the RM10,000 rule: any transaction above it needs its own e-Invoice. What that means for Business Central master data and workflow design.

SCSB explains how Dynamics 365 Business Central handles e-Invoice master data, submission timing and validation, and where HASiL's own rules still apply.

A structured self-assessment for Malaysian finance teams: six measurable symptoms that indicate an accounting package has reached its limit, and when it has not.

By default, no data policies are implemented in a Power Platform tenant, and every employee has access to the default environment.

Licence type determines what each Business Central user can do, and entitlements override any permissions an administrator grants.

Microsoft 365 Copilot readiness is primarily an identity, licensing, mailbox, data-access and change-management question rather than a use-case one.

Power Automate can create approval requests, but a reliable workflow needs defined authority, exception handling and evidence retention.

Microsoft groups Business Central changes into six-month release waves, but the update cycle and maintenance window are what a team actually manages.

Microsoft documents a staged route from Dynamics NAV to Business Central online, and both migration paths pass through Business Central version 14 first.

SCSB sets out the access, retention and ownership decisions that determine whether a document-management platform succeeds or repeats the old file share.

Business Central handles foreign currencies readily, but activating an additional reporting currency converts existing entries and is not a consolidation tool.

A financial report inherits the chart of accounts and dimension design behind it. Settle that before adding any reporting layer.

The costing method cannot be changed once item ledger entries exist, so Business Central inventory setup is decided before go-live rather than corrected after it.

SCSB breaks a Business Central implementation budget into the decisions behind the number: licensing, Malaysian localisation, data, environments and updates.