How does the ONESOURCE integration work?

Gosocket acts as the fiscal issuance and reception platform for ONESOURCE (Thomson Reuters). TR builds and sends tax documents in Gosocket's DTE format; Gosocket validates them, routes them to the appropriate tax authority for the relevant country, and stores the result.

---

The partner model

ONESOURCE operates under a model of unique Partner credentials (Chile) that are reused across the 15 countries in the integration. Each client (company) has its own accountId and ApiKeys, but all operations are authorized using the Partner's token.

---

New client onboarding flow

Before issuing or receiving documents, each company must be onboarded to the platform. Onboarding is asynchronous: createAccount returns a trackId that is polled with getProcess until status = Ok.

1. createTokenPOSTObtains the Partner authentication JWT.2. createAccountPOSTCreates the company account — asynchronous, returns trackId.3. getProcessGETPolls the trackId until status = Ok. Returns the accountId and ApiKeys.

---

Issuance flow (AR)

1. createTokenPOSTObtains the Partner authentication JWT.2. SendDocumentToAuthorityPOSTSends the DTE to Gosocket, which routes it to the country's tax authority.3. GetDocumentPOSTQueries the tax status of the document and retrieves the download URLs.

Argentina: synchronous vs asynchronous

Argentina is the only country with async: true/false support. The integration operates with async: false (synchronous), so the final status is returned in the same SendDocumentToAuthority response.

---

Reception flow (AP)

1. GetReceivedDocumentPOSTQueries received documents in the recipient's Inbox.2. ConfirmReceivedDocumentPOSTMandatory confirmation of reception. Without this step, the document remains pending.3. ChangeDocumentStatusPOSTReports the reception event to the tax authority (commercial acceptance / rejection). Required in CL, CO.

---

Folio Manager (CL and CO)

For Chile and Colombia, issuing documents requires folios previously downloaded from the tax authority. Folio Manager handles this cycle:

billerId

Identifier for the folio manager for a given company and document type. Created with AddBiller and referenced in SendDocumentToAuthority.

Primary range

Block of folios downloaded from the SII (CL) or equivalent (CO). Managed with DownloadPrimaryRangeET.

Sub-range

Partition of the primary range assigned for active use. Automatically reloaded when it falls below the configured threshold.

Automatic reload

Every 2 hours the system checks whether active sub-ranges are below the threshold and, if so, reloads them with the size configured in SaveBillerConfiguration.