Architecture of database
You would need a table for the individual bills, too, would you not?


Table 1: individual bills with external key to table 2
Table 2: Apartments (are "houses" the same as apartments?) with external key to Table 3
Table 3: City information


Your keys would be whatever unique identifier you have set up for each item. 

If houses can hold multiple apartments, then you will need to have another table inbetween Table 2 and Table 3.

and yes, this really are one-to-many relationships between all mentioned tables. 
You cannot have a single bill that can go to multiple apartments, and an apartment cannot be in multiple cities (or houses).