Skip to main content

How does the ONESOURCE integration work?

ONESOURCE (Thomson Reuters) acts as a Partner on the Gosocket platform. 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:

1. createToken
The Partner obtains a 2-hour JWT using their credentials (partnerId + apiKeyUser). Chile is always used as the path country.
2. createAccount
Creates the company account with TaxId, legal name, admin user, authentication method, and digital certificate. Returns a trackId.
3. getProcess
Polls the trackId until status = Ok. On completion, returns the accountId and the client's ApiKeys.

Issuance flow (AR)​

Argentina: synchronous vs asynchronous

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


Reception flow (AP)​


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.