Allocora

Payout export template

Map an Allocora payout export to Hyperwallet OneBatch

Use a reviewed Allocora obligation as the source for a program-specific OneBatch request rather than treating a generic CSV as a native Hyperwallet file.

Create a reviewed payout workspace Download the Generic AP mapping CSV

Direct answer

Hyperwallet Payout Export Template Guide

A Hyperwallet payout export template should carry a known payee identifier, payment amount, three-letter currency, unique client reference, and valid purpose code. Hyperwallet OneBatch uses XLS, XLSX, or XML—not Allocora’s CSV—so the generic export must be mapped into the program-specific OneBatch template before upload.

Reviewed expected payout obligations by payee before external Hyperwallet processing.

Generic payout fields that can guide a program-specific OneBatch mapping.

Statement and run references for post-payment reconciliation.

Required mapping

Hyperwallet OneBatch mapping baseline

A program-specific OneBatch request normally combines a known program and payee identifier with the payment fields required by the active Hyperwallet configuration.

  • Program identifier
  • Accepted payee identifier
  • Payment amount
  • Three-letter currency
  • Unique client reference
  • Valid purpose-of-payment code
  • Optional memo or description

Limitations

What this page does not promise

  • Allocora does not generate a native OneBatch file.
  • Its generic CSV cannot be uploaded directly.
  • Program identifiers, purpose codes, currencies, and payee identifiers vary.
  • Allocora does not create payees, upload requests, process payments, or receive Hyperwallet webhooks.

Use this asset

Move from one-off analysis to a governed close

The free asset helps you preview the workflow. A workspace adds source imports, mapping checks, calculation runs, statement output, payment-ready exports, reconciliation, and audit history.

Download generic payout rail CSV Download generic AP / bank payment CSV
  1. 01 Calculate and lock payout obligations in Allocora.
  2. 02 Export the reviewed payee reference, amount, currency, client reference, and memo context.
  3. 03 Map those values into the XLS, XLSX, or XML OneBatch template for the active Hyperwallet program.
  4. 04 Validate the required program, payee, purpose-code, and currency fields before upload.
  5. 05 Approve and process the request in Hyperwallet; keep Allocora as the calculation evidence layer.

Source-backed answers

Source-backed answers about Hyperwallet OneBatch mapping

These answers use current Hyperwallet documentation to keep generic Allocora CSV evidence separate from program-specific OneBatch request files and payment processing.

What does a Hyperwallet OneBatch payment request require?

Hyperwallet OneBatch accepts XLS, XLSX, or XML request files. Payment requests use a program and payee identifier plus required payment amount, currency, client reference, and purpose code. Exact identifiers and other fields depend on the program configuration, so the Allocora CSV is only a mapping source.

Sources

Product boundary

Allocora calculates, explains, exports, reconciles, and proves expected obligations. It does not move money, collect bank credentials, provide KYC/AML, or file taxes.

Turn this asset into a repeatable workflow

Create a free workspace, use sample data or templates, and review calculation evidence before external payout execution.

Create a reviewed payout workspace View Pricing