Chinese Fapiao Management

Registered by Eric Caudal - www.elico-corp.com on 2013-09-12

The objective of the module is to allow the users to manage the fapiao documents (Official Chinese invoice, emitted and received) as document management system.
It does not include the accounting moves or accounting processes

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

2 Fapiao Management Module
This section introduces the customizations and configurations to make on the Fapiao Management Module
2.1 General information
The objective of the module is to allow the users to manage the fapiao documents (emitted and received) as document management system.
It does not include the accounting moves or accounting processes
2.2 Definition
“Fapiao” in this document refers to the official Chinese document used as invoice by the companies.
“Hong Fapiao” will refer to credit notes from official Chinese document point of view.
“Invoice” will refer to OpenERP invoice.
3 Module definition
3.1 Fapiao Object

The following information will detail the modifications or configurations to be done in the interface of the Fapiao object
(tables are not clean in text...)

Name in OpenERP EN Description, Specification, Comments
1.Fapiao type Customer or supplier, Customer Credit note, Supplier Credit note Mandatory

2.Tax type 13%, 17%, normal, no tax (etc.)
deductible / not deductible VAT. Mandatory, default=normal

3.Partner Related Partner (one-to-many with OpenERP partner) Mandatory

4.Fapiao number Official number Mandatory

5.Fapiao date Date printed on the fapiao Mandatory

6.Reception date For supplier Check if necessary for sending Customer fapiao
7.Amount with taxes Mandatory

8.Invoices m2m OpenERP invoices

9.Tags For document search M2m

Notes

3.2 Views
Fapiao List view:
Partner,
fapiao date,
fapiao number,
Invoice number,
amount

Fapiao Search view:
Partner,
fapiao date,
fapiao number,
Invoice number,
tags

Fapiao Group view:
Partner,
fapiao date,
fapiao number,
Invoice number

3.3 Other modifications
In the Invoice form view, the list of related fapiao should be added as tree form in a separate tab.

4 Fapiao Procedure
4.1 General Procedure
The section includes the procedure to follow for the fapiao management.

Step 1: a fapiao is received or emitted
Step 2: The document is scanned as image
Step 3: a new fapiao is created in OpenERP
Step 4: the scanned document is uploaded to the newly created object as attachment.
Step 5: fapiao allocation to invoice.
If the fapiao is received after invoice, the related invoices can be chosen at fapiao creation.
If the fapiao is received before invoice, need to wait for fapiao allocation against invoice.
Step 6: fapiao payment: no special management (assumption: fapiao payment will be deducted from invoice payment which is 90% of the cases). Cf below discussion.
4.2 Cases study – Fapiao payment
4.2.1 Assumption
Assumption for managing fapiao payment in OpenERP:
Assumption 1: only invoice payment is managed in OpenERP. The link between fapiao and payment is done via invoice.
Assumption 2: we manage fapiao payment with another tool that invoice payment.

We need to define cases study of MEF3 before defining how to record fapiao payment because it's strongly related to bookkeeping procedure.
4.2.2 Case study (first draft)
1. Invoice = payment = fapiao: ok.
2. Invoice = payment + write off = fapiao + fapiao write off. Usually write off = fapiao write off. No problem. If write off <> fapiao write off, it will imply a gap to be explained.
3. 1 invoice = 1 payment = several fapiao: ok.
4. 1 payment = several payments = several fapiaos:
1. If 1 payment = 1 fapiao: ok.
2. If not, difficult to manage without a tool “fapiao payment management”.
5. 1 fapiao = 1 payment = several invoices: ok.
6. 1 fapiao = several invoices = several payments: ok if sum (payment)=fapiao amount.

This case study will be done in details in the MEF3 case study related to the bookkeeping.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.