ManPageW InvoiceSchedule

From ADempiere
Revision as of 13:47, 14 December 2006 by CarlosRuiz (Talk) (Added version and category)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.

Return to Index

Enjoy it, and help to fill it! But please, always respecting copyright.

Please write your contributions under the Contributions Section



Window: Invoice Schedule

Description : Maintain Invoicing Schedule

Help : The Invoice Schedule Window defines the frequency and cut off dates for generating summary invoices. If a customer requires a single invoice for multiple shipments you would define the appropriate invoice schedule and associate it with the Customer.



Tab: Invoice Schedule

Description : Define Invoice Schedule

Help : The Invoice Schedule Tab defines the frequency for which batch invoices will be generated for a Business Partner.

Table Name  : C_InvoiceSchedule

ManPageW InvoiceSchedule InvoiceSchedule.png

Fields

Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. AD_Client_ID

NUMBER(10)

TableDir

Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. AD_Org_ID

NUMBER(10)

TableDir

Name Alphanumeric identifier of the entity The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. Name

NVARCHAR2(60)

String

Description Optional short description of the record A description is limited to 255 characters. Description

NVARCHAR2(255)

String

Active The record is active in the system There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.

There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.

IsActive

CHAR(1)

YesNo

Default Default value The Default Checkbox indicates if this record will be used as a default value. IsDefault

CHAR(1)

YesNo

Amount Limit Send invoices only if the amount exceeds the limit The Amount Limit checkbox indicates if invoices will be sent out if they are below the entered limit. IsAmount

CHAR(1)

YesNo

Amount Amount Amount Amt

NUMBER

Amount

Invoice Frequency How often invoices will be generated The Invoice Frequency indicates the frequency of invoice generation for a Business Partner. InvoiceFrequency

CHAR(1)

List

Invoice on even weeks Send invoices on even weeks The Invoice on Even Weeks checkbox indicates if biweekly invoices should be sent on even week numbers. EvenInvoiceWeek

CHAR(1)

YesNo

Invoice Week Day Day to generate invoices The Invoice Week Day indicates the day of the week to generate invoices. InvoiceWeekDay

CHAR(1)

List

Invoice weekday cutoff Last day in the week for shipments to be included The Invoice Week Day Cutoff indicates the last day of the week a shipment must be made to be included in the invoice schedule. InvoiceWeekDayCutoff

CHAR(1)

List

Invoice Day Day of Invoice Generation The Invoice Day indicates the day of invoice generation. If twice monthly, the second time is 15 days after this day. InvoiceDay

NUMBER(10)

Integer

Invoice day cut-off Last day for including shipments The Invoice Day Cut Off indicates the last day for shipments to be included in the current invoice schedule. For example, if the invoice schedule is defined for the first day of the month, the cut off day may be the 25th of the month. An shipment on the 24th of May would be included in the invoices sent on June 1st but a shipment on the 26th would be included in the invoices sent on July 1st. InvoiceDayCutoff

NUMBER(10)

Integer

Contributions