---
title: "Credit card credits"
slug: "sage-intacct-user-guide-credit-card-credits"
description: "Record credit card refunds from negative-total bills or receipts in MakersHub. Check Sage Intacct card and entity setup, coding limits, and transaction results."
tags: ["User Guide", "Sage Intacct", "Refund", "Credit"]
updated: 2026-11-04T17:41:09Z
published: 2026-11-04T17:41:09Z
canonical: "support.makershub.ai/sage-intacct-user-guide-credit-card-credits"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.makershub.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Credit card credits

Record a refund to a credit card from the existing negative-total bill or receipt in MakersHub, then check the resulting credit card transaction in Sage Intacct.

For foreign-currency or multi-base-currency work, contact [MakersHub support](https://support.makershub.ai/docs/contact-us) to review your setup against the [Best practices baseline](/docs/sage-intacct-user-guide-best-practices) before proceeding. For Construction coding, see [Check the credit details](/docs/sage-intacct-user-guide-credit-card-credits#mh-check-the-credit-details) below.

*Direct Entity* selects an Intacct location and its associated entity context, or Top level, separately from bill Entity and card ownership. Find it in [Direct Entity explained](/docs/sage-intacct-user-guide-connect#mh-understand-direct-entity); complete the card checks below. Where multi-entity tracking applies, keep the workflow established in [Single-entity and multi-entity configuration](/docs/sage-intacct-user-guide-best-practices#mh-single-entity-and-multi-entity-configuration); changing that setup is not a credit troubleshooting step.

### Choose the right credit route

| **Your intended result** | **Use this route** |
| --- | --- |
| Record a refund against an Intacct card account | Continue here, using the negative-total bill or receipt already in MakersHub. |
| Apply a vendor credit against an AP bill | Use [Apply vendor credits before cash](/docs/sage-intacct-user-guide-bills-and-payments#mh-apply-vendor-credits-before-cash). |
| Send money through MakersHub | Use [Choose the payment action and account](/docs/sage-intacct-user-guide-bills-and-payments#mh-choose-the-payment-action-and-account). |
| Pay the card issuer | Follow your card-payment workflow. Intacct's [charge payoff guidance](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Payoff/charge-payoff-overview.htm) explains its separate accounting process. |
| The credit already exists in Intacct | Inspect the existing transaction and contact support to confirm it before recording another credit. |
| The MakersHub credit already synced as a vendor credit | If MakersHub displays **Already synced as a vendor credit.**, contact support before changing or recreating it. The card action does not convert that linked vendor credit. |

Intacct records a card refund as a negative credit card transaction. See [Credits and negative amounts](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/about-credit-card-txns.htm) for that Intacct treatment.

### Check the card and entity

For a negative-total record, **Payment Account** offers card accounts. Choose it in this order:

1. With **Enable Multi-Entity Tracking** turned on in MakersHub, select the bill’s **Entity**; the card-credit action requires it.
2. Select the intended card in **Payment Account**, rather than an expense G/L account.

With the imported **Locations** list available, card choices include the selected entity's accounts and those of its parent entities. Other listed cards do not establish Intacct access. Changing **Entity** clears an incompatible card, so recheck **Payment Account**. If an entity or card is missing, follow [Choose the connection's Direct Entity](/docs/sage-intacct-user-guide-connect#mh-7-choose-the-connections-direct-entity), then return to this credit.

For an **entity-owned card**, confirm its Intacct owner and that every line's **Entity**, including any child location, belongs to that entity. For a **Top-level card**, check its default location and permitted use; shared ownership does not allow use from every entity. If ownership or access is unclear, check **Company ID** and **Direct Entity** using [Choose the connection context for your work](/docs/sage-intacct-user-guide-working-with-entities#mh-choose-the-connection-context-for-your-work), then contact support before approval. Bill Entity alone does not establish where the credit is recorded; verify the Intacct transaction and line allocations.

In Intacct's single-currency setup, a Top-level card is usable only at Top level in the account's default location. Intacct directs companies with multiple base currencies to create and use cards within one entity. See [Where to create the credit card account](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Account_setup/Credit_cards/charge-card-accounts.htm#Wheretocreatethecreditcardaccount).

For a missing or unusable card, check its Intacct owner, status, expiration, and the Web Services user's access. Intacct excludes expired cards from its dropdowns; [My credit card is not appearing in lists](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Troubleshooting/credit-card-expiration-date.htm) explains that check. A card still listed in MakersHub is not proof that it is active or unexpired.

### Check the credit details

| **Detail to check** | **What reaches the Intacct card transaction** |
| --- | --- |
| Negative line amounts | The signed total of the bill or receipt lines. **Amount Paid** does not choose a separate refund amount. |
| Invoice date | The card transaction date. The **Date** in the mark-paid panel does not replace it. |
| Invoice number | The transaction reference. **Ref** in the mark-paid panel does not replace it. Keep the invoice number populated to help identify the credit and reconcile an uncertain sync. |
| Line coding | At least one line, with a G/L account on each line. An explicit line **Entity** or **Department** overrides the bill's selection; when MakersHub’s **Enable Multi-Entity Tracking** setting is on, every line needs Entity coding. The bill's Entity supplies it when the line has no override. |
| Tax, shipping, and fees | Compare the credit total with its ordinary lines. Separate tax, shipping, or fee adjustments outside those lines are not sent; contact support before approval if the totals do not reconcile. |
| Currency | Confirm the credit and card currency before approval. For foreign-currency or multi-base-currency work, use the compatibility-review route above to review the intended refund amount and currency before proceeding. |

**Amount Paid**, **Date**, and **Ref** are payment details saved in MakersHub. For a new payment record:

1. Set **Amount Paid** to the negative credit total.
2. Retain the panel’s **Date**, which starts with the invoice date.
3. Leave **Ref** blank, or enter it if you need a MakersHub payment reference.

To change the Intacct transaction’s date or reference, edit the invoice date or invoice number instead.

Confirm the vendor's identity. MakersHub can link or create the Intacct vendor during sync, so a card credit does not always need a prelinked vendor. For identity or duplicate concerns, use [Find and link the existing vendor first](/docs/sage-intacct-user-guide-vendors-in-a-multi-entity-company#mh-find-and-link-the-existing-vendor-first), restore the intended **Company ID** and **Direct Entity** using that procedure, then return here.

**With Construction enabled:** The Intacct card credit can include **Project** and **Employee | EQ** personnel/equipment coding. **Cost Code** and **Cost Type** are not recorded on the Intacct card credit from these MakersHub fields, even if selected on the line. Use [Check the transaction in Intacct](/docs/sage-intacct-user-guide-construction-and-real-estate#mh-check-the-transaction-in-sage) and verify coding on the actual Intacct transaction. The additional Construction fields are introduced in [Sage Intacct and CRE](/docs/sage-intacct-user-guide-overview#mh-sage-intacct-and-cre); [Construction & Real Estate in MakersHub](/docs/sage-intacct-user-guide-construction-and-real-estate) covers their setup and use.

### Choose the card action before first sync

**Choose the card route before the approval that triggers Intacct sync.** Ordinary **Approve** can create a vendor credit; the later card action then stops at **Already synced as a vendor credit.**

1. Open the negative-total bill. Use **Additional Options** beside **Approve** to show the mark-paid fields. For a receipt, those fields are already shown.
2. Confirm **Entity** where required and select the intended card in **Payment Account**. Keep **Amount Paid** equal to the negative credit total; the Intacct amount still comes from its lines.
3. Use **Approve & Mark as Paid** for the bill, or **Approve Receipt** for the receipt. Both use the card-credit route for a negative-total record.

| **Approval setting** | **Who needs to use the card action** |
| --- | --- |
| **Sync on First Approval** is off | The approver who completes approval. An earlier card action saves the payment details but does not sync yet; the approval that completes the process must also use the card action. |
| **Sync on First Approval** is on | The first approver whose action triggers sync; the card route is needed then, rather than waiting for final approval. |

Check **Sync on First Approval** using [Check coding, then approve and sync](/docs/sage-intacct-user-guide-bills-and-payments#mh-check-coding-then-approve-and-sync). Saving a card selection earlier does not make a later ordinary **Approve** choose card-credit entry.

Process card credits from their individual bill or receipt. **Accounts Payable** > **Mark as Paid** and **Mark All as Paid** do not create card credits. A payment containing credits but no bills stops at **This payment has credits but no bills.**

### Verify the result

**Verify the Intacct credit even when MakersHub shows paid or advances to another record.** Neither result confirms that the Intacct transaction exists or is correct; reopen the credit and complete the checks below.

| **Result to verify** | **What to inspect** |
| --- | --- |
| The MakersHub credit is saved | Reopen that same record. Approved receipts appear under **Archive > Bills**; use the [archive filtering controls](https://support.makershub.ai/docs/filtering-exporting-bills-from-the-archive) to find it. |
| The saved sync details | For a linked card credit, open the double-check icon, **View Synced Record**, to inspect the saved sync details. |
| Current Intacct transaction details | Use **Refresh sync record** in that dialog for the linked transaction's current details. In Intacct, verify the intended card, negative refund amount, entity, date/reference, and line coding. Check **Project** and **Employee \| EQ** on the actual Intacct transaction when applicable; the MakersHub sync-detail view does not verify those fields. |
| The result of sending changes | For a linked card credit, **Re-sync** at the bottom of **View Synced Record** submits the current details; read the result beside that button. Inspect the resulting transaction in Intacct as well. |
| Intacct posting and the actual refund | Check Intacct's accounting state separately from the issuer's refund/statement. Intacct's **Paid** state and MakersHub's paid indicator are not evidence that the refund has settled. |

In Intacct, open **Cash Management** and the **Credit card transactions** list in the relevant entity. [Credit card transaction fields](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/credit-card-txn-fbf.htm) identifies the card, amounts, and state; [General Ledger posting guidance](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/about-credit-card-txns.htm) explains accrual versus cash/multi-book posting.

For an absent or unclear result, inspect Intacct before entering the credit again. [Sync errors](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-sync-errors) provides recorded failures and the support route; return afterward to this credit's result checks. An empty error list does not establish success.

### Retry or change the credit

**Inspect before retrying or recreating.** The credit can already exist in Intacct even when MakersHub shows an error or has no link. Keep the same credit and invoice number while establishing what succeeded.

| **What you need to do** | **What to check** |
| --- | --- |
| Recover an uncertain first sync | If the first sync is uncertain and there is no Intacct link, contact support before retrying, changing the invoice number, or creating another credit. This also applies when the original submission had a blank invoice number. Keep the original record and reference; a retry is not a guarantee against duplicates. |
| Send unchanged linked details again | The existing transaction is retained; the result is **These details are already recorded.** |
| Change a linked credit | Inspect the existing Intacct transaction first. For corrections you can edit and save on the existing MakersHub record, use **Re-sync** at the bottom of that credit's **View Synced Record**. If the needed fields are locked or the correction is unclear, contact support before re-syncing. Changed details update its linked Intacct transaction, subject to Intacct accepting that update. |
| Change the card or convert a vendor credit | The linked transaction's card cannot be changed, and the card action does not convert an existing vendor credit. Contact support before correcting or recreating either record. |
| Remove or add lines | Verify the resulting Intacct lines and total after any change. A removed trailing line can remain in Intacct at zero; confirm that the remaining lines and allocations reflect the intended credit. |
| Clear a reference, description, or dimension | Clearing these values in MakersHub does not erase their existing Intacct values. Contact support to confirm the correction before another sync; use Intacct's editing guidance below to check that transaction's restrictions. |

Use [Intacct's card-transaction editing guidance](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/edit-cc-txn.htm) for its state-dependent restrictions.

### Account for later Intacct activity

Initial sync and ordinary **Refresh Data** do not import card-credit history or refresh every existing credit. For a linked credit, use **Refresh sync record** in **View Synced Record**; the ordinary **Bills** refresh is not a card-credit history check.

**Check with support before deleting a linked credit in Intacct.** The corresponding MakersHub credit and its link can also be removed after Intacct deletion. For a reversal, confirm its effect on the linked MakersHub record with support as a separate correction.

For an accounting correction, follow [Intacct's delete-or-reverse decision table](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/Delete_or_reverse/delete-or-reverse.htm) for the transaction's origin, payoff, payment, and reconciliation state. A card transaction used to pay an AP bill follows [Intacct's separate void procedure](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Transactions/Delete_or_reverse/void-a-cc-txn-used-to-pay-a-bill.htm). Neither is a general instruction to delete and recreate this credit.

**Intacct reference: later charge payoffs**

A later [negative charge payoff](https://www.intacct.com/ia/docs/en_US/help_action/Cash_Management/Payment_Methods/Credit_card/Payoff/negative-charge-payoff.htm) can produce a negative AP bill treated as a vendor credit. That later payoff does not make the original card credit the vendor-credit workflow described in Bills and payments.

### Recover and return to the credit

| **What stops the task** | **Next check** |
| --- | --- |
| **Select an entity for this transaction.** | Set the bill Entity where required and inspect each line's Entity override, then reselect the card if it was cleared. |
| The result says the card belongs to another entity | Confirm the intended card and its Intacct owner. Correct the credit's Entity coding using [Working with Sage Intacct entities](/docs/sage-intacct-user-guide-working-with-entities), then return to this same credit. |
| A card-transaction permission failure | Follow [After changing permissions](/docs/sage-intacct-user-guide-connect#mh-after-changing-permissions). Maintain the application access configured for the Web Services user, save all permission changes, and complete its verification sequence before returning here. If Test Connection is absent, complete support verification using [If Test Connection is unavailable](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-if-test-connection-is-unavailable). **Test Connection** checks read access; it does not exercise every Add/Edit permission. |
| The intended vendor cannot be linked or used | Use [Vendors in a multi-entity company](/docs/sage-intacct-user-guide-vendors-in-a-multi-entity-company) to confirm identity, ownership, and access. Restore the intended **Company ID** and **Direct Entity** using [Choose the connection's Direct Entity](/docs/sage-intacct-user-guide-connect#mh-7-choose-the-connections-direct-entity), then return to the credit. |
| A linked vendor-credit or different-card refusal | Keep the existing records and contact support before changing or recreating them. |

For a sign-in, lockout, or connection-hold message, follow [Sign-in, lockouts, and connection holds](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-sign-in-lockouts-and-connection-holds), then return to [Verify the result](/docs/sage-intacct-user-guide-credit-card-credits#mh-verify-the-result) and [Retry or change the credit](/docs/sage-intacct-user-guide-credit-card-credits#mh-retry-or-change-the-credit). Restored access does not confirm the original sync. Keep the same credit/reference and use the uncertain-first-sync support route when applicable.

If the result remains unclear, contact [MakersHub support](https://support.makershub.ai/docs/contact-us) with the MakersHub credit, Intacct transaction reference if available, intended card/entity, action taken, and exact message. Include whether the issuer refund is actually present. Share these details without passwords.

Return to [Bills and payments](/docs/sage-intacct-user-guide-bills-and-payments) for AP/vendor-credit work, [Best practices](/docs/sage-intacct-user-guide-best-practices) for configuration checks, or [Overview](/docs/sage-intacct-user-guide-overview) to choose another task.