Integrations & security
SilvERP connects to the systems you keep, records every message it exchanges with them, and governs every user — human or automated — by the same permissions.
Connectors that exist, not a roadmap
Microsoft Dynamics 365 Business Central
Retail documents pushed to Business Central, with field mapping per tenant and a per-tenant switch that is off by default.
e-Invoicing (IRN)
Tax invoices registered for an IRN, with retries and cancellation handled in the product.
Banking
Bank connectivity for payins, payouts and virtual accounts, with reconciliation in Finance. Specific bank connections are set up during implementation.
KYC verification
Identity and document verification through KYC providers, at the thresholds your regulator sets.
Market data
Spot prices and FX from market-data feeds and liquidity providers, feeding every module that prices metal.
Email & WhatsApp
Templated notifications per business event, with a delivery log of what actually reached the recipient.
Every exchange is on record
Each module keeps an interface log: one row per call attempt to an outside system, with the full request and response (credentials redacted), status, duration and the document it concerned. Failed attempts are never purged automatically, so "why did this fail twice before it worked?" always has an answer.
How SilvERP protects your data
Access to the action
Permissions are granted per module and per action — who may approve, cancel or settle — not per screen.
Tenant, entity and branch isolation
Every record carries its tenant and entity, and every query is scoped to them — one customer, entity or branch never sees another's rows.
Signed tokens
Sessions use short-lived RS256-signed access tokens and rotating refresh tokens. Only the core service can issue a token; every other service verifies it.
Multi-factor and single sign-on
Authenticator-app second factor for staff, and single sign-on through your identity provider.
Two audit logs on every record
A field-level change history (old value, new value, who, when, from where) and a separate status history for every document.
Impersonation on the record
When support acts on a user's behalf, the audit row names both the person who acted and the account they acted as.
Encryption
Traffic is encrypted in transit; stored documents can be encrypted at rest.
Approvals before posting
Configurable approval rules and an approvals inbox in every module, so a limit breach stops before it posts.
Privacy requests
Data-subject export and erasure requests are handled in the product and recorded in the audit log.
Hosting, backup and recovery arrangements depend on the deployment model and are agreed per engagement. We are happy to walk your security team through the architecture.