Systems
Billing / ERP / Finance
GST-correct invoices out; reconciliation back.
What this class of system is
These are the accounting, ERP, and finance systems the hospital books revenue in.
orophin speaks CSV, a REST API, and the GST e-invoicing API. Out: invoices and charges for accounting; in: reconciliation. Vault and Falcon consume and produce the data.
Everything above rides one path. The on-prem orophin agent speaks the protocol on the hospital's own network and opens a single outbound mutually authenticated link to the Pensieve backend. Your network team approves egress.
On the wire
What it emits, and what carries it
The traffic
Finance systems want a posting. What leaves is an invoice and a ledger line with the tax treatment already resolved, and what returns is a settlement the invoice can be matched against. The e-invoicing route is different in kind: an invoice is registered with the Invoice Registration Portal and comes back with a reference number that has to be stored against the bill it belongs to.
What breaks here
Tax is decided by context. The same drug is exempt inside an inpatient bill and taxable across the retail counter, and a bed is taxed or exempt depending on the room class and the rate. Vault carries the tax treatment as an attribute of the charge at the moment the charge is captured, so the invoice is correct when it is raised rather than corrected in the ledger afterwards.
Protocols
The standards this class speaks
Each one is described in full on the standards register, at the anchor named here.
- CSV / flat fileThe fallback for a system with no live interface. orophin watches a drop folder for scheduled exports and reads each file once.
- DB polling / CDCRead-only polling of a legacy database or a view, where no messaging exists at all. orophin reads; it never writes back into someone else’s schema.
- mTLS WebSocket bridgeThe single outbound, mutually authenticated link orophin opens to the Pensieve backend. Both ends verify a certificate, nothing listens on the hospital side, and every row in this register rides it.
- SAML SSOEnterprise sign-in for a hospital with an existing SAML identity provider.
- OIDC SSOOpenID Connect sign-in for a hospital identity provider.
- GST e-invoicing APIIndia’s e-invoicing rails. Vault produces GST-correct invoices for the Invoice Registration Portal, with the tax treatment carried as an attribute of the charge rather than applied at the end.
Members
Systems in this class
8 entries on the register, each at its own anchor.
- TallyCSV / REST API, GST e-invoicing. Out: GST-correct invoices and ledgers to accounting.
- SAPREST API / CSV, SAML SSO. Out: financial postings. In: master data.
- Oracle ERPREST API / CSV, SAML SSO. Out: financial postings. In: master data.
- Microsoft DynamicsREST API / CSV, SAML SSO. Out: financial postings. In: master data.
- Zoho BooksREST API / CSV, GST e-invoicing, OIDC SSO. Out: invoices and ledgers to accounting.
- GST IRP portalGST e-invoicing API. Out: e-invoices to the Invoice Registration Portal.
- Payment gateway (UPI)REST API (UPI), OIDC SSO. In: payment confirmation matched to the invoice.
- Bank reconciliation feedCSV / REST API. In: settlements matched to invoices.
What a name in this register means
Compatibility only. Pensieve connects to systems in this class over the protocol they speak. Naming a system describes the connection Pensieve is built to make; it implies no partnership, no certification, and no existing deployment.