Skip to main content

Movements

Movements represent the real money flows detected in your bank accounts and are a key component of APIO’s reconciliation process.

In APIO, bank movements are retrieved through Khipu, which provides access to bank transaction data.

How Movements Are Obtained​

  • APIO connects to your bank accounts via Khipu
  • Khipu retrieves transaction movements from the bank
  • These movements are stored in APIO and used for reconciliation

Usage Limits and Pricing​

Movements retrieval is subject to monthly call limits, which depend on the pricing plan contracted with APIO.

Important considerations:

  • Each synchronization with Khipu consumes API calls
  • There is a maximum number of movement fetches per month
  • Exceeding the contracted limit may require upgrading your plan or adjusting sync frequency

For this reason, APIO recommends configuring movement synchronization intervals carefully.

Role in Reconciliation​

Movements are the data source used to match against expected payments:

  1. Expected payments are generated from invoices registered in the SII
  2. Movements are fetched from bank accounts via Khipu
  3. APIO compares amounts, dates, and references
  4. When a match is found, the payment is marked as reconciled

Key Notes​

  • Movements are essential for accurate reconciliation
  • Availability depends on Khipu connectivity and bank support
  • Call limits are enforced according to your APIO pricing plan

By combining expected payments from SII invoices and movements obtained via Khipu, APIO provides a reliable and auditable reconciliation process.