The Spanish version is the authoritative reference. View in Spanish
ONESOURCE — Integration
ONESOURCE is the tax compliance platform of Thomson Reuters (TR). TR uses Gosocket to issue and receive tax documents in 15 countries through a REST API with OAuth 2.0 authentication.
What does the Gosocket + ONESOURCE integration do?
Supported countries
| Country | Code | Certificate | taxEntity |
|---|---|---|---|
| Argentina | ar | ❌ Not required | ❌ Not required |
| Bolivia | bo | ✅ .pfx / .p12 | ✅ ISIPASS token |
| Brazil | br | ✅ .pfx / .p12 | ✅ NDD credentials + reception emails |
| Chile | cl | ✅ .pfx | ❌ Not required |
| Colombia | co | ✅ .pfx | ❌ Not required |
| Costa Rica | cr | ✅ .p12 | ✅ ATV credentials (receipts) |
| Ecuador | ec | ✅ .p12 / .pfx | ❌ Not required |
| El Salvador | sv | ✅ .pfx / .p12 | ✅ MH credentials |
| Guatemala | gt | ✅ .pfx / .p12 | ✅ SAT credentials |
| México | mx | ✅ CSD .cer + .key | ❌ Not required |
| Panamá | pa | ✅ X.509 v3 | ✅ RUC + DGI code |
| Paraguay | py | ✅ .pfx | ✅ idCSS + css SIFEN |
| Perú | pe | ✅ .pfx / .p12 | ✅ SOL credentials (SUNAT) |
| República Dominicana | do | ✅ .pfx / .p12 | ✅ certification (boolean) |
| Uruguay | uy | ✅ .pfx | ❌ Not required |
Chile is the ONESOURCE reference country: the Partner credentials (partnerId / apiKeyUser) are created for Chile and reused for all other countries.
Who is this documentation for?
This documentation is aimed at:
- ONESOURCE architects and engineers who design and implement the tax integration with Gosocket
- Thomson Reuters technical teams who onboard, configure and support accounts on the platform
- Technical partners who operate the integration in production across the 15 countries
Integration mechanism
The integration uses REST API with OAuth 2.0 authentication. ONESOURCE acts as a Partner: it obtains a JWT with its Partner credentials (partnerId + apiKeyUser), creates customer accounts asynchronously via Onboarding, and issues documents with SendDocumentToAuthority using Gosocket's generic DTE mapping. Reception operates by polling with GetReceivedDocument. For Chile and Colombia, issuance requires folios managed by the Folio Manager.
See How it works for details on the Partner model, flows and the onboarding cycle.
Where to start
If this is your first time working with this integration, follow this order:
- Read How it works to understand the Partner model, async onboarding and the issuing and reception flows
- Get the Partner credentials at Onboarding
- Create the first customer account with createAccount and verify the result with getProcess
- Review the Flows for the issuing and reception call sequence
- If you operate in CL or CO, configure the Folio Manager before issuing
Sections in this documentation
How it worksGuidePartner model, async onboarding, issuing and reception flows, and Folio Manager.OnboardingREST APIPartner credentials and methods for creating and managing customer accounts.Country ParametersReferenceConditional taxEntity and certificateRootDto fields specific to each country.Process FlowsFlowsIssuing (AR) and reception (AP): authentication, sending, status query and events.Folio ManagerREST APIFolio Manager configuration for managing ranges and folios (CL, CO).