Hum...
I'm looking to your code and I think there is something strange about it...
See, the pagination works because when you use a TableRecords associated with an aggregate, before running the aggregate, the system goes look for the Start Index and Line Count in the Table Records. This way, when running the aggregate, the system optimizes it to go fetch only the number of records that will be shown, starting at the row defined in the TableRecords (in this case, a value returned by a function).
But when I look your preparation and the properties of the table records, what I am seeing is that the "list" that is the source of the table records is receiving its items from a Server Action (PesquisaFaturas2). Is that correct?
If so, I would say that it will not work, as the Server Action does not have access to the Table Records and will ignore the Start Index defined by the function in the Page.
Also, this will cause problems, as the system will not be able to optimize aggregates inside the Server Action...
Cheers.