Skip to main content

Onboarding

To activate any services related to reconciliation, APIO requires a dedicated onboarding process handled directly by the APIO team.

This applies to all integrations involved in the reconciliation flow, including:

  • Retrieving expected payments from the SII
  • Retrieving bank movements via Khipu

Why Onboarding Is Required​

Both SII and Khipu integrations involve:

  • Sensitive financial and fiscal data
  • Secure credential management
  • Regulatory and compliance requirements

For this reason, these integrations cannot be self-activated by merchants.

SII Onboarding​

For SII integration, the APIO team is responsible for:

  • Validating invoice sources
  • Configuring access to SII-registered invoices
  • Mapping fiscal documents to APIO’s expected payments model

This ensures expected payments are correctly generated from official tax records.

Khipu Onboarding​

For Khipu integration, the APIO team handles:

  • Bank account linking
  • Permission and scope configuration
  • Validation of available banks and accounts
  • Configuration of movement synchronization limits based on your plan

This guarantees secure and reliable access to bank movements.

Onboarding Flow​

  1. The merchant requests reconciliation activation
  2. APIO coordinates onboarding with SII and/or Khipu
  3. Credentials and permissions are securely configured
  4. Data flows are validated
  5. Reconciliation features are enabled in APIO

Key Notes​

  • Onboarding is mandatory for reconciliation-related services
  • Both SII and Khipu integrations require APIO intervention
  • Activation timelines depend on external platform validation

By centralizing onboarding, APIO ensures a secure, compliant, and reliable reconciliation setup for all merchants.