2015-11-26 6:42 GMT-05:00 Cédric Krier <[email protected]>:

> On 2015-11-26 06:05, Carlos Eduardo Sotelo Pinto wrote:
> > Dear Developers
> >
> > There is one error on the last line on the last mail
> >
> > Is mandatoy that
> >
> > - Parties that are "Natural people" must have ballet, must no be possible
> > use other kind of document
> >
> > - Parties that are "Legal people" must have invoices, they could ask fo
> > ballet if they want, but ballet dont generate "fiscal credit"
> >
> > If a company dont use both of then when separated accounting, could have
> > legal issues and could have real big penalties
>
> For the last time, I will repeat.
> You are only talking about layout and display but never ever you have
> talked about the accounting moves and the tax reports.
> So we can only guess that indeed there is no differences on this topic
> and so for me, you can solve the issue by using different journals and
> customize the numbering base on the journal.
>
> PS: Many localization has required different numbering option for the
> invoice. I'm pretty sure a generic solution should be to use the
> MatchMixin pattern with a list on the fiscalyear.
>

​

After talking with an accountant friend, her explain me that is no need to
have two differnt views, however, is really important having two different
clients ( natural parties and legal parties )

- Natural parties, they are the default parties using simple invoicing,
which is the default invoicing
- Legal parties, they are companies or business, using normal invoice

Diferences

- Normal invoince is for legal parties, and the id is used for the
goverment authority, cause it will be used for follow taxes and payments
- Simple invoice is used for natural parties o final consumers

Caracteristhics

- Both types of documents ( simple and normal invoice are just selling but
must be reported on diffrent reports, making diference betweem them for the
goverment authority
- ON the accounting, selling are just selling and the invoice printed is
just a type f report for the client, however must have a flow, something
like that

1. Register client and client type ( natural or legal )
2. Create a sell
3. Print invoice
3.1 If is a legal party, normal invoice must be printed

When a report is done:
1. One repot for simple invoices
2. One report for normal invoices

Please, help on what will be the best solution for it


> --
> Cédric Krier - B2CK SPRL
> Email/Jabber: [email protected]
> Tel: +32 472 54 46 59
> Website: http://www.b2ck.com/
>
> --
> You received this message because you are subscribed to the Google Groups
> "tryton" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tryton/20151126114228.GG29932%40tetsuo.wifi.b2ck.com
> .
>



-- 
Carlos Eduardo Sotelo Pinto
    Senior Software Analyst Developer
    Claro RPC +51983265994 | MOV RPM( # ) +51 966110066
    GTalk: [email protected] | Skype: csotelop
    GNULinux RU #379182 | GNULinux RM #277661

No availability between 08:30 and 18:00, I will answer as soon as posible

Please consider the environment before printing this email
Join the campaign at http://thinkBeforePrinting.org

-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/CAEhw%3DE8Tmh%3DTx7RdjToYX%3DUnHxAcEE_HyzedSArJR6PAYTfb6Q%40mail.gmail.com.

Reply via email to