Hi Everyone,

The purpose of this post is to help all the AP and AR clerks out there who like to see a due date or due day on their invoice.

The challenge: The ADempiere and iDempiere derive the due date based on the payment terms. One field that is noticeably missing is the anticipated due date or due day.

The Solution: The below solution makes it easy to add the due date or due day to the invoice window.

ColumnSQL: ColumnSQL is ADempiere and iDempiere’s way of adding a virtual column. You want to add a new entry with the following details:

  • Login: System Administrator Role
  • Window: Table & Column
  • Tab: Column
  • Action: Create a new column with the following columnSQL

ColumnSQL to create your Due Day text:

(to_char(paymentTermDueDate(c_invoice.C_PaymentTerm_ID, c_invoice.DateInvoiced), 'Dy DD Mon YYYY'))

Here is an image of the solution:

ADempiere iDempiere Invoice Due Date-resized-600

Now, add this field to the invoice windows:

  • Login: System Administrator Role
  • Window: Window, Tab & Field
  • Tab: Field
  • Action: Create a new field record that points to the above column.
  • Note: you can simply add “paymentTermDueDate(c_invoice.C_PaymentTerm_ID, c_invoice.DateInvoiced)” without the date formatting and set the Table and Column => Reference field = “Date”. This way iDempiere interpret the date according to your locale.


Here is a picture of the final product:

ADempiere iDempiere Invoice Due Date Day Techincal Training-resized-600

If you want to add this field to other places like the Aging Report, let me know.

I hope this helps!!

Why consider Open Source ERP

Open source ERP gives you every opportunity to prove or disprove its ability to support your company’s ERP needs on a timeline that satisfies your organizational needs. With open source ERP, you do not face the same financial constraints nor do you face the same conflicts of interest as with commercial ERP. Instead, you invest in the appropriate skills and knowledge for your people and processes. Best of all – if open source ERP cannot solve your company’s needs, you can safely justify spending the additional $2K to $5K per person per year for life of your commercial ERP to help drive your organization’s success.

ADempiere vs iDempiere vs Openbravo vs Compiere

The ADempiere, iDempiere, Openbravo and Compiere environments are amazingly similar. iDempiere came from ADempiere. ADempiere and Openbravo came from Compiere. Compiere came from Jorg Janke. Jorg came from Oracle. As a result, iDempiere and ADempiere have much in common with Oracle’s ERP in terms of the financial feature set.

This is both good and bad. Good because iDempiere and ADempiere are quite capable to help a company grow beyond $500M USD. Bad because they tend to be more complex in that they account for multiple languages, accounting schemas, currencies, calendars, costing types, costing methods, etc…. If you are a growing organization, and you need a system that will grow with you, and you have the right internal talent/resources, iDempiere or ADempiere will be a big asset for you.

The biggest difference between these products is that ADempiere and iDempiere are pure open source. ADempiere and iDempiere make all feature available for free. Compiere and Openbravo hold back features behind a commercial or paid license.

iDempiere and ADempiere vs OpenERP:

iDempiere/ADempiere (iD/AD) and OpenERP approach ERP from two very different directions. OpenERP comes out of the box with very simple options. If you are coming from QuickBooks, and you need a simple ERP system help you manage your business, OpenERP will look and feel comfortable.

iD/AD comes out of the box with every feature installed and configured to run a $200M+ USD business. If your business is growing rapidly, and you are willing to invest the time to learn an enterprise accounting system, then iD/AD will give you confidence.

Which one is best for you depends on your internal talent, growth and business complexity. Here is a post to help you learn more.



Leave a Reply

Your email address will not be published. Required fields are marked *