Start a conversation

Reconciling CallStream Invoice Beneficiary Details, Entity Changes, and Partial Credit/Reissue Amounts

Overview

You may see conflicting beneficiary/bank details when comparing an older CallStream invoice (issued under a previous contracting entity) with the currently published CallStream bank details. This can also appear as an amount dispute (for example, “it isn’t 600.00 it is 1050.00”) when a balance was partially credited and reissued under a new entity.

This article explains why these differences occur and how to safely reconcile beneficiary information, invoice history (including “-New” reissues), and credit memo amounts for audit and AP purposes.

Solution

Issue: Invoice shows different beneficiary/bank details than the current bank-details reference

How to recognize this issue (common symptoms)

  • Your invoice beneficiary name differs from the beneficiary name shown in CallStream’s current bank-details reference.
  • You see an invoice for one amount (for example, £1,050) but a credit memo exists for a different amount (for example, £600).
  • You see a reissued invoice with a suffix like <invoice_id>-New and are unsure how it relates to the original invoice.
  • Your AP team requests a “full credit” for the original invoice amount, but only a partial balance was credited and reissued.

Root cause

This scenario can happen when CallStream’s contracting entity changes and billing documents span the change period. See CallStream Ownership for the published ownership-change statement and confirmation that historical invoices can show different invoicing entities from the latest invoices:

  • December 6, 2023: CallStream Ltd was transferred to Kaxxa Technologies FZ-LLC (formerly ESW Technologies FZ-LLC).
  • January 1, 2025: ownership was subsequently transferred to ESW Operations, LLC, the current contracting entity and beneficiary used for payment instructions.

In addition, an invoice can be partially credited, and the credited portion can be reissued under the new entity, creating multiple related documents:

  • Original invoice: <invoice_id> (issued under the former entity)
  • Credit memo: <credit_memo_id> (covers only the transferred portion, not necessarily the full original invoice)
  • Reissued invoice: <invoice_id>-New (issued under the current entity for the transferred portion)

Important clarification: If you see older invoices listing Kaxxa Technologies FZ-LLC, that does not mean Kaxxa is the current beneficiary. For current payment instructions, the beneficiary is ESW Operations, LLC, and the authoritative bank details are maintained in the “CallStream’s Bank Details” knowledge article in the CallStream support portal.

Resolution: Reconcile beneficiary details and invoice trail safely

1) Do not pay until the beneficiary is verified

  1. Verify the beneficiary using the official “CallStream’s Bank Details” reference in the CallStream support portal.
  2. If there is still a mismatch between the invoice and the current bank-details reference, pause payment and contact CallStream Billing to confirm which beneficiary/bank details must be used for that specific invoice.

Do not rely on bank details copied from emails or informal documents. Use official sources and billing confirmation to prevent misdirected payments.

2) Determine whether your invoice was reissued (and for how much)

Gather (or request) the complete document set:

  • The original invoice: <invoice_id> (amount: <original_amount>)
  • Any credit memo(s) applied to the original invoice: <credit_memo_id> (amount: <credit_amount>)
  • Any reissued invoice: <invoice_id>-New (amount: <reissued_amount>)
  • A short explanation of how balances moved (example: “<credit_amount> was transferred and reissued under the new entity”).

Key rule: A credit memo for the full original invoice amount is only valid if the original invoice was fully voided/credited. If only part of the balance was transferred and reissued, then a “full credit” for the original amount would be incorrect.

3) Reconcile payments by date and amount (AP/bank trace)

  1. Match CallStream’s confirmed “last payment received” details (date and amount) to your bank ledger.
  2. Apply the payment against the correct document in your AP system:
    • If the payment corresponds to the reissued invoice (<invoice_id>-New), your AP system should reflect that linkage.
    • If your AP system only retained the original invoice, you will typically need both:
      • the credit memo (to reduce/transfer the original balance), and
      • the reissued invoice (to represent the payable under the new entity).

Example from a documented case: the invoice was confirmed as paid, and the last payment received was £600 on July 20, 2025. Use the date/amount to trace the payment in your bank records and align it to the correct invoice document.

4) Documentation requests (auditors / letterheaded confirmation)

  • If auditors require proof of an entity/name change, use the published CallStream Ownership article, which states the ownership-change dates and explains why historical and latest invoices can show different invoicing entities.
  • If you request a letterheaded statement, note that bespoke letterheaded confirmations may not be available—especially if the requested statement would not reflect the current contracting entity (for example, requesting confirmation of an “ESW → Kaxxa” change when CallStream is now under ESW Operations, LLC).

Validation (how to confirm the issue is resolved)

  • The beneficiary used for payment matches the official current bank-details reference (or is explicitly confirmed by Billing for that invoice).
  • The original invoice, credit memo(s), and any -New invoice tie together into a single consistent audit trail.
  • Invoice status (for example, “paid”) and payment date/amount details can be matched by your AP team to bank records.

Frequently Asked Questions

1. How do I know I’m affected by this same issue?

If you see a mismatch between (1) beneficiary/bank details printed on an invoice and (2) CallStream’s current bank-details reference, or you see an invoice amount (for example, £1,050) but a credit memo for a different amount (for example, £600), you are likely seeing an entity-change and/or partial credit + reissue scenario.

2. Why does my invoice say “Kaxxa Technologies FZ-LLC” if CallStream is under “ESW Operations, LLC”?

CallStream Ownership states that CallStream Ltd was transferred to Kaxxa Technologies FZ-LLC on December 6, 2023 and subsequently to ESW Operations, LLC on January 1, 2025. It also explains that invoicing entities were updated after each change, so historical invoices can differ from the latest invoices. For current payment instructions, rely on the official “CallStream’s Bank Details” reference in the support portal (or Billing confirmation for the specific invoice).

3. Why isn’t the credit memo for the full invoice amount (for example, why “£600” instead of “£1,050”)?

A full credit memo is only valid if the original invoice was fully voided/credited. In a partial credit + reissue process, only the transferred portion is credited (for example, £600) and then reissued on a new invoice (for example, <invoice_id>-New) under the current entity. In that case, a “full £1,050 credit memo” would be incorrect because the original invoice was not fully credited.

4. What should I do if the invoice beneficiary/bank details don’t match the current bank-details reference?

Pause payment and verify beneficiary details using the official “CallStream’s Bank Details” reference in the support portal. If there is still a mismatch, contact CallStream Billing to confirm the correct beneficiary/bank details for that specific invoice before paying.

5. Can I request a letterheaded statement confirming the entity/name-change details for auditors?

Use the published CallStream Ownership article for audit evidence. Bespoke letterheaded confirmations may not be available—especially where the requested statement would not reflect the current contracting entity (CallStream is currently under ESW Operations, LLC).

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Matthew Mrosko

  2. Posted

Comments