ceven

Chaser

Automates the collection of overdue payments by syncing invoice data, triggering tailored reminders, and updating customer contact records based on payment behavior.

Try Chaser in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Chaser integration

    • Describe the outcome and Ceven picks the right Chaser calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Chaser data, across all 30 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Chaser access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Chaser, when, and on whose behalf.
    • The agent pauses and asks when Chaser is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Chaser.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Chaser action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Chaser, and when to use it.

Create Invoice
Use this to push a new invoice record into Chaser after verifying the customer already exists in the system.
Get Credit Notes
Pull a list of all credit notes to reconcile offsets against outstanding balances.
Get Customer by ID
Retrieve full details for a specific customer using their external source system ID.
Get Customers
Pull a complete list of all customers to process contact updates or status audits.
Get Organization
Pull organization details including currency, timezone, and legal info to configure workflow logic.
Create Credit Note
Use this to generate a credit note after an invoice adjustment or dispute is approved.
Create Customer
Establish a new customer record in Chaser before attempting to upload invoices.
Update Customer
Modify existing customer info like contact email or payment terms using their external ID.
Update Invoice
Modify an existing invoice to change the status, amount, or due date.
Search Customers
Find customers by name or email to avoid creating duplicate records.
List Overdue Invoices
Pull all invoices that have passed their due date for targeted reminder workflows.
Delete Invoice
Remove an invoice record if it was created in error or fully voided in the source system.

12 actions · scroll to see them all

Frequently asked questions

Ceven uses a search first approach to prevent duplicate records. Before calling the Create Customer action, the agent queries Chaser using the external ID from your accounting software or the primary email address. If a match is found, the agent updates the existing record instead of creating a new one. This ensures that your communication history remains tied to a single customer entity, which prevents the system from sending multiple reminders to the same person under different account IDs. You can configure the workflow to prioritize specific identifiers, such as a VAT number or a company registration ID, to ensure the highest possible match accuracy across your datasets.
Yes. By connecting your email provider to Ceven, the agent can monitor incoming messages for keywords related to invoice disputes or payment queries. When a relevant email is detected, the agent uses the Update Invoice action to change the status or apply a pause to the reminders in Chaser. This prevents the awkward situation where a customer is actively talking to your team about a problem while still receiving automated prompts to pay. Once the dispute is resolved in your CRM or accounting tool, Ceven can automatically resume the reminder sequence or mark the invoice as settled, keeping the communication loop closed.
Chaser imposes specific rate limits on their API to ensure platform stability, which can be a bottleneck for organizations syncing tens of thousands of invoices at once. Ceven manages this by implementing an exponential backoff strategy. If the agent receives a 429 Too Many Requests response, it pauses the workflow and retries the request after a short delay, gradually increasing the wait time. For massive bulk uploads, the agent batches the requests into smaller chunks. You will see a notification in the workflow log if a process is slowed down due to rate limiting, ensuring you know why a sync is taking longer than usual.
Ceven handles multi currency workflows by first calling the Get Organization action to identify the base currency and timezone of your Chaser account. When creating invoices or credit notes, the agent passes the currency code provided by your source accounting system. If there is a mismatch between the source system and Chaser, the agent can be programmed to flag the record for manual review or apply a conversion rate from a third party data source. This ensures that the amount requested in the reminder email matches the amount recorded in your ledger exactly, avoiding confusion for international clients.
Absolutely. You can build a workflow where a specific trigger, such as an approved refund request in Zendesk or a status change in Salesforce, prompts Ceven to use the Create Credit Note action in Chaser. The agent pulls the original invoice ID, calculates the credit amount, and pushes the record to Chaser. This immediately reduces the outstanding balance for that customer, which in turn stops any automated reminders for that specific amount. This end to end flow eliminates the need for a finance person to manually enter the credit note in two different systems.
The agent leverages the Update Customer action to keep contact data fresh. If your CRM indicates that a company has changed its accounts payable contact, Ceven can automatically push that updated email address to Chaser. You can also set up workflows that rotate contacts if a primary email bounces, moving the reminder to a secondary contact or a general finance inbox. By keeping the contact layer in sync, the agent ensures that your reminders actually reach a human who can authorize payment, rather than disappearing into a dead inbox.
Yes. Ceven can act as a bidirectional bridge. For example, the agent can pull a list of overdue invoices using the Get Customers and list actions in Chaser and then update a custom field in Salesforce to mark an account as high risk. This alerts the account manager that there is a payment issue before they jump on a renewal call. You can also sync the date of the last reminder sent so that your sales team knows exactly when the customer was last contacted about their debt, preventing redundant outreach.
Ceven requires API access with permissions to read and write customers, invoices, and credit notes. Depending on your Chaser tier, you may need to generate an API key from the administration panel. Once connected, the agent operates within the scope of the user who provided the credentials. If that user does not have permission to delete invoices or modify organization settings, the agent will receive an access denied error from the Chaser API. We recommend using a dedicated service account with the specific permissions needed for your workflows to maintain a clean audit trail.

Alternatives to Chaser

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Quadient logoQuadientTesorio logoTesorioGaviti logoGaviti

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Chaser and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free