The Universal Adapter Standard

The "Tower of Babel" Problem

Financial integration is historically painful because every system speaks a different language:

• Banks speak SFTP and flat files (BAI2, AI, CSV).
• ERPs speak OData, SOAP, or SQL.
• Modern Apps speak REST JSON.

Traditionally, developers write custom Python or C# scripts to bridge these gaps. These scripts are brittle, insecure, and hard to maintain.

The Demiton Solution: 5 Verbs

Demiton replaces custom scripts with a Universal Adapter Framework. We treat every external system (whether it's CommBiz or Dynamics 365) as a generic "Data Source" that supports 5 universal operations:

1. FETCH_DATASET (Read)

• Concept: "Go get bulk data."
• SFTP: Downloads a file from /outbox.
• OData: GETs a list of entities (e.g., VendorsV2).
• Result: Data is normalized into a standard JSON dataset in memory.

2. PUSH_DATASET (Write)

• Concept: "Send bulk data."
• SFTP: Uploads a generated file (ABA) to /inbox.
• OData: POSTs a journal batch.

3. LOOKUP (Enrich)

• Concept: "Find a specific detail."
• Use Case: During a bank reconciliation, take a Customer Reference Number (CRN) from the bank statement and LOOKUP the matching Invoice ID in D365 to verify the amount.

4. EXECUTE_COMMAND (Action)

• Concept: "Trigger a remote job."
• Use Case: Tell D365 to "Post Journal" after the lines have been uploaded.

5. WAIT_FOR_EVENT (Governance)

• Concept: "Stop and listen."
• Use Case: The workflow pauses. It sends a card to Microsoft Teams. It does not proceed until a human clicks "Approve."

Why this matters for Security

By abstracting the protocol, we abstract the Risk.

• Your developers never see the SFTP private key.
• The key is stored in our Secure Vault, encrypted with AES-256.
• The Adapter retrieves the key only at the millisecond of execution, performs the handshake, and wipes it from memory.