Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

License: AGPL-3

Credit Card Payments

This module provides a way to record Credit Card purchases and to pay them the same way regular purchases are recorded (via Vendor Bills) and paid (via Vendor Payments).

By default, if vendor bills are used to record credit card purchases, the liability (AP) from the supplier/vendor must be moved to the credit card company via a manual journal entry.

Because a journal entry contains less information than a vendor bill, there may be a loss of information that affects book keeping accuracy and the ability to properly reconcile the AP amount when the credit card statement arrives and needs to be settled. This method also requires an additional step not needed when a vendor bill is paid via bank or cash.

This module automates the creation of the manual journal entry required to move the AP to the credit card company, retains all information about the purchase in an invoice document, and leverages the standard purchase and payment workflow already in place for bank and cash payments.

It supports as many Credit Cards as are needed, configured in the same way an additional payment method would be (i.e. via the creation of a new journal).

To settle a Credit Card statement, the regular workflow to record a vendor payment is used – allowing the removal of charges not included in the statement. Non-purchase transactions like fees for annual membership, balance transfers, cash advances and foreign transactions; as well as charges for late payments and returned checks; can be entered either as Vendor Invoices or manual Journal Entries as users elect.

Both of these methods will allow these items to be settled when making a payment to the credit card company.

This module also supports payment cancellation and re-entry (in the case a mistaken amount is entered) as well as refunds (where the purchase is returned and a credit from the credit card company will be issued).

Installation

  • No specific installation required.

Configuration

  • Go to Accounting > Configuration > Journals

  • Create a new journal for your credit card

  • Check the box ‘Transfer AP to Credit Card Company’ and set the ‘Credit Card Company’ field

Usage

To use this module, you need to:

  1. Go to Accounting > Purchases > Vendors Bills

  2. Select an open bill and click on Register Payment

  3. Select the credit card journal and validate the payment

Try me on Runbot

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.

Credits

Images

  • Odoo Community Association: Icon.

Contributors

Funders

The development of this module has been financially supported by:

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit https://odoo-community.org.

Metadata

Release files for odoo10-addon-account-payment-credit-card 10.0.1.0.0.99.dev10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo10-addon-account-payment-credit-card 10.0.1.0.0.99.dev10
File Interpreter ABI Platform Actions
odoo10_addon_account_payment_credit_card-10.0.1.0.0.99.dev10-py2-none-any.whl Python 2 none any Details for odoo10_addon_account_payment_credit_card-10.0.1.0.0.99.dev10-py2-none-any.whl

Release files / odoo10_addon_account_payment_credit_card-10.0.1.0.0.99.dev10-py2-none-any.whl

Download URL odoo10_addon_account_payment_credit_card-10.0.1.0.0.99.dev10-py2-none-any.whl
Size 20.4 kB
Tags Python 2
SHA-256 checksum
How to use checksums
85bf40fc4273d8d577eebf15ec8d3ab0b53aaf63ba7f6240aa82431bda1dd89a
BLAKE2b-256 checksum
How to use checksums
2e67d5a6919974f5faf456e476f14fb0517ef4050782b53eb5f9c5bbacf39ff6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3

Security for odoo10-addon-account-payment-credit-card 10.0.1.0.0.99.dev10

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page